4 ms·
I see. Wasn't aware of this. I considered taking SQLite for my current stack, but dismissed it because I've read lot of bad stuff with concurrency. However, it
by TheRoque 2y ago
I see. Wasn't aware of this. I considered taking SQLite for my current stack, but dismissed it because I've read lot of bad stuff with concurrency.
However, it says that it doesn't work over networks, so basically you can't do WAL with a containerized stack ?
- hruk 2y agoYou can have multiple containers on the same host use the same db via Docker volumes - we have a number of production services set up this way.
- adamtaylor_13 2y agoAs hruk pointed out, you can use docker volumes to solve for this. However, you can also ship multiple DBs depending on your use-case. If it's a shared DB, it's probably not a great idea for micro-services. But if you're building a majestic monolith, there's few reasons NOT to go with SQLite. Especially paired with litestream[0]. 0: https://litestream.io/ https://litestream.io/