3 ms·

I think we disagree on the "most cases" aspect that For most of the things I touch, having a single-point-of-failure data store is typically not acceptable for

I think we disagree on the "most cases" aspect that For most of the things I touch, having a single-point-of-failure data store is typically not acceptable for production environments, except perhaps caching.

danielmarkbruce 4y ago
If you are a good software engineer, you probably work at a place that needs good software engineers, which by definition tends to be a place with a system that needs high availability or low latency or both or something else, while serving a lot of customers or load or something, all of which basically results in a pretty complicated distributed system... So in your day to day job as a good software engineer, yeah sqlite isn't going to be a good choice. It doesn't work well for the sorts of systems you work on. But if you were going to build a new social network for your college or something trivial like that, and you just want to move fast and have a crazy simple deployment setup, you might well use sqlite.