3 ms·
TBH, if I were you, I would wait until they see the cracks starting to form for themselves. Containerization isn't perfect, and has its own challenges. There w
by bunderbunder 7y ago
TBH, if I were you, I would wait until they see the cracks starting to form for themselves.
Containerization isn't perfect, and has its own challenges. There will be growing pains as you move to it, especially if most the team is unfamiliar with the technology. If you try to push it before people perceive (for themselves) that they are experiencing some of the problems that it's designed to solve, then, on top of all that, you're going to have an audience that sees it as a solution in search of a problem.
Conditions like that are just about perfect for kicking off a chain of events that leads to yet another "Containerization is the worst idea ever, never containerize anything" blog post entering the world.
- dtjohnnyb 7y agoAppreciate the measured warning, as you mentioned there's a lot of strong opinions either way so it's hard to find the more practical advice among it all which is what inspired the original question. I'll take all the advice here and get better understanding of the overheads and pain myself (and hopefully a few other interested folk) so that when the cracks do start showing properly there's a working containerized solution to roll out more smoothly.