DevOps and “Shifting Left”
One of Agile’s principles is “continuous improvement”, a fundamental borrowed from the Japanese “Lean” manufacturing approach called Kaizen. Consider DevOps as a passageway that extends the “continuous improvement” Agile practice not only into development and testing (DevQA) but also into operations.
Getting DevOps right doesn’t mean overloading your developers and QA personnel; it means making fundamental changes to the way in which development, testing, and operations teams work together.
As organisations embrace a DevOps approach, they’re known to be “shifting left” — as in shifting Operations responsibilities to an earlier stage of the software delivery lifecycle. “Shifting left” requires a pragmatic review of your software development lifecycle and aim to reduce risk continually, simplify deployments & increase your team’s delivery velocity.
"Doing" DevOps requires teams to architect software in a better and more efficient way with micro-services packed as immutable containers (or VMs), tested and deployed continuously to servers that are automatically provisioned with configuration management tools for fast, reliable and continuous deployments that can scale to any number of servers and with the ability to roll-back.
In short, DevOps touches the whole "microservices" development and deployment lifecycle and organisations that incorporate DevOps practices simply get more done.
Some of the top drivers for DevOps include improved time to production, business value and cost savings, however embarking on a DevOps journey will indeed yield substantial benefits like:
- Faster delivering of product features
- More effort is spent adding value (rather than fixing and on maintenance)
- Reduced complexity
- Resolve issues quicker
- Improved software stability
Thank you for your feedback Roman Revyakin I always welcome the opinions of others, and I look forward to reading about some of your insights. All the best.
Yuan Heng Fan: quoting from the above article (and the one before): "Doing" DevOps requires teams to architect software in a better and more efficient way with micro-services packed as immutable containers (or VMs), tested and deployed continuously to servers that are automatically provisioned with configuration management tools..." If that statement does not sound to you like microservices are implied for doing DevOps than yes, your reading is quite different to mine :-)
Roman Revyakin Maybe I read this post quite different as you did but I see no statement made by Jacobus K.de by Jacobus K. that DevOps is Microservices or vice versa. To me it's one of the good approaches that we can do DevOps right and I personally find it very helpful. Everyone can be very opinionated and sometime I do enjoy a déjà Vu moment. Well done Jacobus Kloppers
I am having a deja vu moment, Jacobus. What's the point of the second article having exactly the same content as the previous one? Also, while microservices are awesome they are by no means equal "DevOps". And vice versa. You can do microservices without DevOps and you can do DevOps without having a heck of a clue about microservices.