3 ms·
I'm not thinking 1000s of servers, because that is extremely rare, but this definitely doesn't apply to only non-critical private stuff. Many orgs have up to a
by franga2000 4y ago
I'm not thinking 1000s of servers, because that is extremely rare, but this definitely doesn't apply to only non-critical private stuff. Many orgs have up to a dozen servers, each running multiple services. If you have multiple replicas of certain servers, you can reboot them (or just restart the impacted services) one at a time with no disruption.
The thing is, you usually aren't building everything from scratch. A pretty typical containerized web app deployment might consist of postgres, redis, elasticsearch, nginx, task queue and app server containers. Each of these needs to be updated and you're probably only building two of them from Dockerfiles. Instead of just your host distro, you're now waiting on the maintainers of all of these images to push updates that you can pull. Big distros get updates early so they can push them out the instant the embargo lifts, but I doubt all of these Docker packagers and statically-built software maintainers do. You're either stuck waiting or you have to build all of them from scratch.
- alanfranz 4y agoIf you’re a small org with just a dozen servers and you’re overcomplicating your life with hundreds of containers, then I agree with you. But you can’t attack containerization if it’s used by proper orgs with the right scale.