DevOps means a lot of things to a lot of people. But one thing that is consistent with those who are DevOps fans is that DevOps is a way of operating, not a definition of any particular setup.
A limited number of organizations were born in the DevOps era. And many organizations have missed the container train.
One of the key benefits of microservices is that each service can have its own lifecycle. In other words, each service can be built, deployed, monitored, and managed independently of other services.
In traditional application environments, meeting compliance goals required paying attention to infrastructure like physical devices, unified data stores, and static networks.
Perhaps the most difficult dimension of DevOps is that DevOps never ends. There is no guide to doing DevOps, and there is no final setup that means you have completed your DevOps journey.
Like many people in the IT industry, when I first heard about Docker, I expected it to be yet another fad. After all, containerization is not something that is new to Linux. Tools like LXC, Virtuozzo and OpenVZ all offer to run your OS and apps in a container and share resources. They all were around well before Docker.
Over the last several years, Kubernetes has become an indispensable tool for organizations that use containers on a large scale. As great as Kubernetes is, however, there are some things that could make it even better.
Kubernetes is a cornerstone piece of open source technology in the container management and orchestration space. It includes all of the pieces necessary to provide a true highly available infrastructure for container-based services running on multiple public clouds, private clouds, or even bare metal.
"Docker vs. virtual machines: Which should you use?"
Team Oracle + Wercker would like to invite you to try out the next generation of Steps!
Build, test and deploy like never before with the power of Wercker
Third party Integration
Support on Slack