I made an angel investment in Drifting in Space coming out of the YC W22 batch. DIS is the company behind Jamsocket, an infrastructure provider for “session-lived backends” based on the open source project Spawner. Paul and Taylor, founders of the company, previously spent time building data-heavy applications at great engineering orgs like Two Sigma and Datadog.
Other than having really enjoyed my meetings with them, I think Jamsocket could be a core piece of software infrastructure for many applications going forward. There's a few trends that have been already talked about over the last couple of years, but have yet to gain major traction due to the technical overhead required to support them:
- As the industry moved from on-prem to cloud, the architectural design of the backend hasn’t drastically changed. We still mostly treat the cloud as a shared on-prem for all of our customers. Having to support all customers on the same backend leads to code that is highly over-engineered for the average use case, but necessary for the top percentile of users. There’s no easy way to separate the two and size the infrastructure for each customer's load size.
- For data-intensive applications, it does matter which hardware is used, especially when it comes to GPUs. If you look at TensorFlow benchmarks for example, training a model on an A100 card instead of 1080 Ti is almost 5x as fast. As a customer, I should have the option to select the specs for my machine, like Deepnote does for example, but it's not trivial to build this. Jamsocket can make it easier to offer that option to all customers.
- Offering real-time collaboration on SaaS products has been a real differentiator for products like Google Docs, Figma, Miro, etc and I expect more products to offer this in the future. If you read Figma’s CTO post on how their multiplayer tech works you can see how hard it’d be for the average company to build this from scratch.
I'm really excited to see the team execute on this!
This is part of a broader interest I have in “heterogeneous computing”, which I put in quotes because it’s not the traditional definition. For example, what if hardware selection was inferred by the type of compute that is going to be run, instead of being static? What if your ORM was routing your data to different databases based on the type of queries usually run on it?
My email is on the homepage, always happy to chat about this stuff!