4 ms·
Lesson: if you start a new database company, start with SQL. Almost every DB that starts without SQL support eventually ends up adding it back in later.
by the_duke 2y ago
Lesson: if you start a new database company, start with SQL.
Almost every DB that starts without SQL support eventually ends up adding it back in later.
- 1st1 2y agoTrue. In our case it's not that simple. By resisting adding SQL early on we were able to advance our data model & schema without SQL holding us back. And now we've added SQL in such a way that it takes full advantage of our stack.
- lmm 2y agoThat's like saying you should start with microservices/kubernetes/etc. because every company ends up needing those things. IMO you should delay adding SQL as long as possible so that it doesn't compromise your design.
- ndriscoll 2y agoNot using SQL makes it basically a complete non-starter for any business unless it had some extremely compelling niche feature that you absolutely need and can't be found elsewhere. SQL has a massive ecosystem around it. All the examples I see are either some bespoke typescript library, or treat queries as strings. Obviously it can't hook into any of the zillion query builder libraries out there, and you'd have to go implement one or write a decent amount of code for an existing one to be able to use it. I also don't see any docs for JVM usage at all, which is like half the industry. If you want to experiment with syntax for database queries, macros that translate to SQL at compile time seem like a much better way to get traction, but pretty much everything I've seen ends up being a more verbose cosmetic variation of SQL. The one big flaw to fix is that SELECT should have been at the end.