In this article we review the book Infrastructure as Code - Managing Servers in the Cloud written by Kief Morris, who is leading Continuous Delivery and DevOps at ThoughtWorks Europe. In over 300 pages, Morris lays down the foundation for Infrastructure as Code and outlines the main patterns and practices recommended for building it.
Mirco Hering explains why we shouldn't leave COTS products (and the people working on them) left behind in a DevOps world. With creative solutions we can apply good practices from custom software. This leads to a significant effort reduction in the long term.
This article addresses a topic that is not fully covered in current IT world: live migration of containers, how it works behind the scenes, and what problems it solves.
The fifth annual QCon New York was the biggest yet, bringing together over 850 team leads, architects, project managers, and engineering directors.
The article discusses a catalog of configuration smells, provides a few examples of such smells along with corresponding refactorings, and lists a few tools that could be used to reveal such smells. 2
Framed in the story of the author's car catching fire, this article describes five ways of thinking to help understand DevOps culture, and behaviours necessary to create an effective DevOps team. 1
With the fast-pace of cloud changes, cloud lock-in remains a popular refrain. But what does it mean, and how can you ensure you're maximizing your cloud investment while keeping portability in mind?
Consultants play a major role in helping companies deliver software. How do these consultants tackle lock-in and build portable solutions? In this interview, OpenCredo's Nicki Watt tackles this topic.
Cloud bursting! On-premises! Hybrid cloud! Off-premises! Multi-cloud! Each of them makes logical sense, but it’s the last - multi-cloud - that the author has been seeing in actual practice the most.
There's no shortage of opinions on the topic of technology lock-in. InfoQ reached out to four software industry leaders to participate in a lively virtual panel on this topic.
It makes no difference how hard you try- some form of lock-in is unavoidable. What matters most is understanding the layers of lock-in, and how to assess and reduce your switching costs.
This is the second article of a two article series in which we try to work from an abstract level of IoT reference architectures towards a concrete architecture for actual use cases. 1