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.
One thing every developer can—or at least should—agree upon is that testing software is an integral part of the software development process. If it were up to the development team, no application would be released without rigorous testing, ensuring no bugs made their way into production.
A limited number of organizations were born in the DevOps era. And many organizations have missed the container train.
My journey to DevOps has been long and storied. I’ll stop short of saying it was troubled, but there was definitely trouble along the way. Let me explain…
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.
One main reason to use containers is that they help make apps, services and environments highly scalable. But that doesn’t happen magically. In order to take full advantage of the benefits of containers, you have to build your stack and configure your environment in ways that maximize scalability.
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.
Docker is the hot topic at every tech conference, developer forum, and DevOps team meeting today. However, Docker isn’t the only (or the first) container technology. In fact, Docker itself was originally based on another container framework, Linux containers (LXC), which has been around for a decade.
Since our acquisition announcement in April the Wercker team has worked non-stop with our colleagues at Oracle to build our shared vision.
Build, test and deploy like never before with the power of Wercker
Third party Integration
Support on Slack