3 ms·
> If the application only runs on one server, then definitely SQLite. That means you do not need fail over, replication or other fancy features. Why not simple
by chipdart 2y ago
> If the application only runs on one server, then definitely SQLite. That means you do not need fail over, replication or other fancy features. Why not simple SQLite?
I agree. So many usecases require a bounded context, and even ephemeral data stores. Memory caches are all the rage but the cost of doing network calls to fetch data from a memory cache can eclipse the cost of simply fetching the data from a local disk.
- ammo1662 2y agoI experienced that an application randomly throw exceptions when trying to access the SQL Server in the same PC. And finally we found that it is caused by a broken firewall software. A traditional DBMS is a quite complex application, sometimes using that may introduce more bugs than your application itself.