DevOps
The benefits of moving to new modern application architectures like Micro Services and runtimes like Docker are well accepted. Most organisations that see IT as a core part of their business are either adopting these new application and runtime architectures or looking to move towards them over the coming years.
Exploring the value of a UI for DevOps and Automation tooling – and looks at why User Experience is becoming more important as tools become more widely adopted.
There are two fundamental approaches of how to design automation processes – declarative and imperative.
How do we define the boundaries and constituent parts of what DevOps is really all about?
As the adoption of Automation techniques and tools start to move more into the mainstream, more progressive organisations are looking at how smaller units of automation can be invoked in a more efficient and responsive way. One of the ways they are looking to achieve this is through Event Driven Automation.
One of the most common questions I am asked in the course of my work at MidVision is “What is the difference between [replace as appropriate] Puppet / Chef / Ansible / Salt – and RapidDeploy?” (It may also be followed by “We already use Puppet”).
Move from Continuous Integration to Continuous Delivery with Jenkins and RapidDeploy
How To Implement DevOps Practices in highly regulated industries – Agile, Continuous Delivery and much more | MidVision Application Release Automation
