I say this every time convex comes up in a conversation: by far my favorite stack for building web apps.<p>The developer experience is really polished.<p>I haven't deployed any major apps yet, so unsure how the costs scale VS deploying your own or other BaaS offerings.<p>The team is incredibly skilled and great people.
Curious about the choice to send requests with WebSocket connections instead of just plain old POST forms. This precludes anyone with javascript disabled from using any of these sites. I don't think there's anything in the business logic preventing it
Well, I've only used convex for some hobby projects, and I must say; It allows me to build real-time applications without having to configure websockets, and it allows me to build applications pretty fast.
Did yall build all the database implementation components yourself, or are any of them open source / off the shelf? It sounds like Kafka could do the transaction log job, and overall the architecture sounds similar to XTDBv1 which does use Kafka for that component.<p><a href="https://v1-docs.xtdb.com/concepts/what-is-xtdb/" rel="nofollow">https://v1-docs.xtdb.com/concepts/what-is-xtdb/</a><p>I’m also curious if you support unique constraints on non-id columns, or if having writer actions close to the database kind of takes that role.
> Instead, we can check whether any of the writes between the begin timestamp and commit timestamp overlap with our transaction’s read set.<p>Do you handle the case where the actual objects don't overlap but result of an aggregate query is still affected? For instance a `count(*) where ..` query is affected by an insert.
How can we be sure you are going to be around when the inflation hits 9% and interest rates go up to 15% ? This is a serious question because whoever invests time in building on your backend which is not open source are taking extreme risks.