I have had a version of the following conversation more than a few times with community members trying to sort out where to run their containerized apps in production: User: So, where should I run my containers? Bare metal or VM’s Me: It’s not a question of “either / or” – that’s the beauty of Docker. That choice is based solely on what’s right for your application and business goals – physical or virtual, cloud or on premise. Mix and match as your application and business needs dictate (and change). User: But, surely you have a recommendation. Me: I’m going…
written by John Willis, Evangelist at Docker The Third Way of DevOps completes the full cycle. It has also been referred to as just “Continuous Learning”. In DevOps speak, we sometimes allude to the word Kaizen as a method of continuous improvement in an organization. This “Kaizen” being achieved through a culture of continuous experimentation and learning throughout all activities in an organization.
written by John Willis, Evangelist at Docker In the previous post in this series, we discussed patterns of applying DevOps principles in a way that yields high performance outcomes. In part two, we are going to discuss what is called “The Second Way”. This second “way” is ultimately about amplifying and shortening feedback loops such that corrections can be made fast and continuously. This is sometimes referred to as the right to left flow. A defect is not a defect unless it hits the customer. Lean principles teach us that the earlier we can catch a potential downstream defect, the…
written by John Willis, Evangelist at Docker Have you read Gene Kim’s The Phoenix Project? Some of the principles behind the Phoenix Project and an upcoming book I am co-authoring with Gene (The DevOps Cookbook) have been referred to as the “Three Ways of DevOps”. These are particular patterns of applying DevOps principles in a way that yields high performance outcomes.