| ▲ | childintime 3 hours ago | |||||||
Is it time to kill the database and replace it with a LLM optimized compiled version that simply implements the required API directly in (Rust) code, without any dynamic overhead? It probably will still be based of off a base design or a base file format. Ultimately this system will encompass the whole OS, of course, but the DB might be the best place to start. | ||||||||
| ▲ | tyre 3 hours ago | parent | next [-] | |||||||
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. | ||||||||
| ||||||||
| ▲ | nemothekid 3 hours ago | parent | prev | next [-] | |||||||
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. | ||||||||
| ▲ | bijowo1676 2 hours ago | parent | prev | next [-] | |||||||
SQLite already exists and some people use it | ||||||||
| ▲ | dymk 3 hours ago | parent | prev | next [-] | |||||||
Is it time to get rid of hammers and replace them with swiss army knives? | ||||||||
| ||||||||
| ▲ | eatonphil 3 hours ago | parent | prev | next [-] | |||||||
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. | ||||||||
| ▲ | Ostatnigrosh 3 hours ago | parent | prev [-] | |||||||
Unless you're tigerbeetle and want to handroll every single thing you do lol | ||||||||