I like containers—I really do.
They provide a built-in architecture for and reward a distributed systems approach to development, and they offer portability.
Indeed, a good deal of my work involves designing and deploying containers, both for existing and new applications.
But there can be too much of a good thing, and I see signs that containers are used where they don’t fit.
It’s common for technologists to chase the hype cycle, and containers are the current flavor of the month.
They’re sometimes adopted because they’re trendy, not because they’re the right technology.[ To the cloud! Real-world container migrations. | Dig into the the red-hot open source framework in InfoWorld’s beginner’s guide to Docker. ]
As a result, IT is spending too much money and time trying to force-fit an application’s round peg into a container’s round hole.To read this article in full or to leave a comment, please click here