upvote
You mean get rid of Postgres and build bespoke database-esque systems for every use case?

If so, then no. It is not time for that.

reply
Yeah, I'm struggling to come up with a really good time for that.

The best I got is if you are trying to do an old-school style video game asset/save game storage. But even then, the value in just using sqlite or even parquet is really high.

There's so many really good data formats that deciding on a new one at this point seems pretty silly. Particularly because what you sign up for when you make a new one is losing any and all tools that could be used to work with and diagnose that data.

reply
Instead of a database, the LLM will expose an api endpoint and build a database on demand?

That's interesting. Maybe to decrease latency the LLM could "cache" it's build of it's database and reuse in between instances. It could host this artifact on a "hub" of git trees and then any new use cases that come up, can be added to this git tree. Then it can possibly be reused in different use cases.

reply
SQLite already exists and some people use it
reply
Is it time to get rid of hammers and replace them with swiss army knives?
reply
We could build a new hammer for each nail!
reply
I have seen this happening already at two different companies. And I'm also doing it as well. Particularly for search indexes where there's no risk of data loss.
reply
Unless you're tigerbeetle and want to handroll every single thing you do lol
reply