4 ms·
Side question: is there a good rule of thumb for when an application can start benefitting from using a database? I'm working on a project whose internal data
by skohan 5y ago
Side question: is there a good rule of thumb for when an application can start benefitting from using a database? I'm working on a project whose internal data structures are starting to resemble a database, and I've been considering moving from just using language-native data structures to an in-memory sqlite instance, but I'm not sure what the tradeoffs are.
- pvillano 5y agoReasons to use a database: * to save data * to query data with SQL
- contravariant 5y agoOn the most basic level databases solve the ACID problem, namely that you typically want data operations to be: Atomic Consistent Isolated transactions Durable A database may also provided better options for querying, though you'd have to use a pretty odd data model if that's a true bottleneck.