Session-lived Application Backends
driftingin.space
Session-lived Application Backends
1–10 of 17 posts
Re: Session-lived Application Backends
#2Re: Session-lived Application Backends
#3Very cool, excited to see this launch! Similar ethos to ink&switch[0] local-first apps, but taken to their logical conclusion [0] https://www.inkandswitch.com/
Re: Session-lived Application Backends
#4Re: Session-lived Application Backends
#5Re: Session-lived Application Backends
#6Any thoughts on comparisons/contrasts between this and Durable Objects?
Re: Session-lived Application Backends
#7I'm a believer in serverless, and think it could be better still! The continued progress of companies like darklang, replit, singlestore, planetscale (to name a few) have been super exciting.
And so: How'd you compare your approach with James Cowling's convex.dev which is a slightly different take on marrying data with serverless [0]? Thanks.
Re: Session-lived Application Backends
#8It seems that CloudFlare’s Durable Objects are another take on solving this problem. Any thoughts on comparisons/contrasts between this and Durable Objects?
The other difference is that it’s open source. We’re also working on a managed version for people who don’t want to manage a cluster, but we don’t want to tie developers to a managed platform without an open source on/off ramp.
Re: Session-lived Application Backends
#9Congrats on the funding and soft launch. I'm a believer in serverless, and think it could be better still! The continued progress of companies like darklang, replit, singlestore, planetscale (to name a few) have been super exciting. And so: How'd you compare your approach with James Cowling's convex.dev which is a slightly different take on marrying data with serverless [0]? Thanks. [0] https://docs.convex.dev/guide/…
Re: Session-lived Application Backends
#10Congrats on the funding and soft launch. I'm a believer in serverless, and think it could be better still! The continued progress of companies like darklang, replit, singlestore, planetscale (to name a few) have been super exciting. And so: How'd you compare your approach with James Cowling's convex.dev which is a slightly different take on marrying data with serverless [0]? Thanks. [0] https://docs.convex.dev/guide/…
Thanks! Convex looks neat, and you’re right, there is a lot going on at the data and data/frontend layer. Our approach is to provide a generic compute layer with the session-lived backend model, so you can do more than just store data with it.