upvote

points

by franga200012 hours ago |
comments
upvoteby stingraycharles10 hours ago|
next
[-]
“Especially in containerised setups, every "app" gets its own database anyways, and if the app is further broken down into services, they usually communicate between each other and not with a shared database. “

You seem to be talking about a vastly different use case.

Containerized apps having their own database? What? Aren’t these types of containers stateless? I always very much try to keep state out of app containers.

What kind of data storage are we talking about?

reply
upvoteby franga20008 hours ago|
parent|
[-]
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.

reply
upvoteby jappgar5 hours ago|
parent|
next
[-]
And when you need to scale to thousands of instances of your microservice?
reply
upvoteby stingraycharles5 hours ago|
parent|
next
[-]
Yeah 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?
reply
upvoteby jappgar2 hours ago|
parent|
[-]
I just think a lot of people here haven't ever worked on large scale systems. They don't know what the don't know.
reply
upvoteby graerg3 hours ago|
parent|
prev|
[-]
That's the whole thesis; YAGNI.
reply
upvoteby mxey7 hours ago|
parent|
prev|
[-]
Yes if you run a database server like an embedded application database, then it won’t be very different from an embedded application database.
reply
upvoteby HDThoreaun9 hours ago|
prev|
[-]
Every container gets its own database?
reply
upvoteby franga20007 hours ago|
parent|
[-]
Yes? Well, every "app", as I quite explicity wrote. Look up the docker compose file or helm chart for basically any app. I'm running dozens of apps, each with their own postgres, redis and nginx containers alongside the main application server. That's what the stack is designed for.
reply
upvoteby mxey7 hours ago|
parent|
[-]
The Compose file is written like that so you can quickly try the app without setting up extra dependencies. Usually not for production use.

Especially since in production you might want to scale the parts separately. I like to have a Postgres cluster to connect where backup is already handled, and the app then doesn’t have any persistent data, doesn’t need any network volume mounts.

reply