3 ms·
> In practice, when you reach for a database engine you're actually reaching for four basic features: unique constraints, transactions, indices, and history tab
by agentultra 16d ago
> In practice, when you reach for a database engine you're actually reaching for four basic features: unique constraints, transactions, indices, and history tables.
That might be a very specific assumption. What about serializability? Replication? Materialized views? Procedures? Locking? Access control?
It’s cool to experiment and try new approaches. Neat one here.
Could still end up moving to Postgres.
- thom 16d agoWhat about... queries?
- dam_jackalopes 16d ago[dead]
- crabmusket 14d agoYes, this is called out near the end of TFA. Relational databases are great at allowing you to just come up with a new query that combines your data in a new way, express it in SQL, and get results near instantly. It's an architecture that is optimised for flexibility! I don't think I'd want to give that up without a very good reason.