I appreciated this rant by @alicegoldfuss on a impractical parts of running containers. Not many people talk about the downsides.
(shame its not on a blog somewhere where it would be readable)
It's almost like containers only improved the Dev side of DevOps hmmmm how strange
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Hope none of your containers have noisy neighbors because cgroups only go so far.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Iptables? Different with containers? Perf profiling? Much harder with containers.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Hope none of your containers have noisy neighbors because cgroups only go so far.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Orchestrators can redeploy a dead instance but can they detect latency and move it to a better system? Because a slow container is hell.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Everyone using containers means I don't have to wake someone else up to deploy their broken shit. It makes DR much faster, too.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
But that's only half of the ol DevOps pie. The other half? More burden and work. At scale.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Why do you want to do this? Is your current deploy system failing? Do you have a lot of moving parts?
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
You don't need to Dockerize your small, monolithic ecommerce site.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
Do you have an entire team to dedicate to supporting this in prod? Because this is an entire new platform to support and maintain.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
If you have the reasons and the resources, then sure do containers. They can do cool things. Just be informed.
— Alice Goldfuss (@alicegoldfuss) January 26, 2017
The post Why Containers Are Crap appeared first on EtherealMind.