3 ms·
For some strange reason, some people feel like using SQLite all over the place, even when a proper RDMS would be the right answer.
by pjmlp 1y ago
For some strange reason, some people feel like using SQLite all over the place, even when a proper RDMS would be the right answer.
- fidotron 1y agoI recently encountered a shared SQLite db being used for inter process pub sub for real time data . . . in a safety critical system. Wrong on so many levels it's frightening.
- 9rx 1y agoIt is not that strange when you consider the history. You see, as we started to move away from generated HTML into rich browser applications, we started to need minimal direct DBMS features to serve the rich application. At first, few functions were exposed as "REST APIs". But soon enough those few featured turned into full-on DBMSes, resulting in a DMBS in front of a DBMS. But then people, rightfully, started asking: "Why are we putting a DBMS in front of a DBMS?" The trouble is that nobody took a step back and asked: "Can we simply use the backing DBMS?" Instead, they trudged forward with "Let's get rid of the backing DBMS and embed the database engine into our own DBMS!" And since SQLite is a convenient database engine...