781

submitted 5 months ago by devilish666@lemmy.world to c/programmer_humor@programming.dev

74 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] CaptainHowdy@lemm.ee 14 points 5 months ago

If you're doing it right, containers are less like VMs and more like cgroups. If orchestrated correctly it uses less system resources to run lots of services on a single system/node.

That said, I'm a devops/infrastructure/network professional and not a developer, so maybe I'm missing something from the dev experience.... But I love containers.

Docker does kinda suck now, though. Use podman or another interface instead if you can help it.

[-] skuzz@discuss.tchncs.de 7 points 5 months ago

If done correctly, it also forces devs to write smaller more maintainable packages.

Big if though. I've seen many a terrible containerized monolithic app.

[-] dan@upvote.au 7 points 5 months ago

I've seen many a terrible containerized monolithic app.

I've seen plenty of self-hosters complain when an app needs multiple containers, to the point where people make unofficial containers containing everything. I used to get downvoted a LOT on Reddit when I commented saying that separating individual systems/daemons into separate containers is the best practice with Docker.

[-] skuzz@discuss.tchncs.de 2 points 5 months ago

Separate containers works like a dream when one app starts shitting the bed, gets auto-cycled, and everyone else just chills. Not surprised on the Reddit downvotes though. That place is so culty, especially now.