3 ms·
If an app needs a database, it gets a database server container, instead of getting a user and database on a shared database server as things used to be done. E
by franga2000 5mo ago
If an app needs a database, it gets a database server container, instead of getting a user and database on a shared database server as things used to be done. Every little django app has its own postgres container. Every wordpress site gets its own mysql container. That is the modern way.
Those database containers get a PVC/volume/mount for their data dirs. The only thing ever connecting to them is their "owner" application container. So at that point, why not drop the postgres container and PVC mount a sqlite directory in the app container? The result is the same.
- mxey 5mo agoYes if you run a database server like an embedded application database, then it won’t be very different from an embedded application database.
- jappgar 5mo agoAnd when you need to scale to thousands of instances of your microservice?
- stingraycharles 5mo agoYeah this is the part I don’t get. It seems like people are talking about 1 distinct app = 1 container and this is the new normal? We’re back to managing cows instead of cattle again?
- jappgar 5mo agoI just think a lot of people here haven't ever worked on large scale systems. They don't know what the don't know.
- andersmurphy 5mo agoI think a lot businesses build large distributed systems prematurely. They don't know what they don't know.
- graerg 5mo agoThat's the whole thesis; YAGNI.
- andersmurphy 5mo agoWhat on earth needs thousands of instances? Are you building a CDN? Most apps can be a single server or sharded by business/region. Honestly, this whole leys run loads of nodes seems to have sprung up from languages that are slow oe don't have decent concurrency.