{"id":20246,"date":"2023-01-27T07:20:56","date_gmt":"2023-01-27T07:20:56","guid":{"rendered":"https:\/\/www.booksofall.com\/es\/?post_type=product&p=20246"},"modified":"2023-02-07T08:41:06","modified_gmt":"2023-02-07T08:41:06","slug":"ci-cd-with-docker-and-kubernetes-book","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/es\/ci-cd-with-docker-and-kubernetes-book\/","title":{"rendered":"CI\/ CD with Docker and Kubernetes Book"},"content":{"rendered":"

Using Docker for Development and CI\/CD\u00a0<\/a><\/b><\/h2>\n

In 2013, Solomon Hykes showed a demo of the first version of Docker during the PyCon conference<\/a> in Santa Clara2. Since then, the benefits of Docker containers have spread to seemingly every corner of the software industry. While Docker<\/a> (the project and the company) made containers so popular, they were not the first project to leverage containers out there; and they are definitely not the last either.<\/p>\n

Several years later, we can hopefully see beyond the hype as some powerful, efficient patterns emerged to leverage containers to develop and ship better software, faster. In this chapter, you will first learn about the kind of benefits that you can expect from implementing Docker containers.<\/p>\n

Then, a realistic roadmap that any organization can follow realistically, to attain these benefits.<\/p>\n

1.1 Benefits of Using Docker\u00a0<\/b><\/h3>\n

Containers will not instantly turn our monolithic, legacy applications into distributed, scalable microservices. Containers will not transform overnight all our software engineers into \u201cDevOps engineers\u201d. Notably, because DevOps is not defined by our tools or skills, but rather by a set of practices and cultural changes. So what can containers do for us?<\/p>\n

1.1.1 Set up Development Environments in Minutes\u00a0<\/b><\/h4>\n

Using Docker and its companion tool Compose, you can run a complex app locally, on any machine, in less than five minutes. It sums up to:<\/p>\n

$ git clone https:\/\/github.com\/jpetazzo\/dockercoins
\n$ cd dockercoins
\n$ docker-compose up<\/p>\n

You can run these three lines on any machine where Docker is installed (Linux<\/a>, macOS<\/a>, Windows<\/a>), and in a few minutes, you will get the DockerCoins demo app up and running. DockerCoins was created in 2015; it has multiple components written in Python, Ruby, and Node.js, as well as a Redis store. Years later, without changing anything in the code, we can still bring it up with the same three commands.<\/p>\n

This means that onboarding a new team member, or switching from a project to another, can now be quick and reliable. It doesn\u2019t matter if DockerCoins is using Python 2.7 and Node.js 8 while your other apps are using Python 3 and Node.js 10, or if your system is using even different versions of these languages; each container is perfectly isolated from the others and from the host system.<\/p>\n

We will see how to get there.<\/p>\n

1.1.2 Deploy Easily in the Cloud or on Premises<\/b><\/h4>\n

After we build container images, we can run them consistently on any server environment. Automating server installation would usually require steps (and domain knowledge) specific to our infrastructure. For instance, if we are using AWS EC2, we may use AMI (Amazon Machine Images), but these images are different (and built differently) from the ones used on Azure, Google Cloud, or a private OpenStack cluster.<\/p>\n

Configuration management systems (like Ansible, Chef, Puppet, or Salt) help us by describing our servers and their configuration as manifests that live in version-controlled source repositories. This helps, but writing these manifests is no easy task, and they don\u2019t guarantee reproducible execution. These manifests have to be adapted when switching distributions, distribution versions, and sometimes even from a cloud provider to another, because they would use different network interfaces or disk naming, for instance.<\/p>\n

Once we have installed the Docker Engine (the most popular option), it can run any container image and effectively abstract these environment discrepancies.<\/p>\n

The ability to stage new environments easily and reliably gives us exactly what we need to set up CI\/CD (continuous integration and continuous delivery). We will see how to get there. Ultimately, it means that advanced techniques, such as blue\/green deployments, or immutable infrastructure, become accessible to us, instead of being a privilege of larger organizations able to spend a lot of time to build their perfect custom tooling.<\/p>\n

1.1.3 Less Risky Releases\u00a0<\/b><\/h4>\n

Containers can help us to reduce the risks associated with a new release.<\/p>\n

When we start a new version of our app by running the corresponding container image, if something goes wrong, rolling back is very easy. All we have to do is stop the container, and restart the previous version. The image for the previous version will still be around and will start immediately.<\/p>\n

This is way safer than attempting a code rollback, especially if the new version implied some dependency upgrades. Are we sure that we can downgrade to the previous version? Is it still available on the package repositories? If we are using containers, we don\u2019t have to worry about that, since our container image is available and ready.<\/p>\n

This pattern is sometimes called\u00a0immutable infrastructure<\/b>, because instead of changing our services, we deploy new ones. Initially, immutable infrastructure happened with virtual machines: each new release would happen by starting a new fleet of virtual machines. Containers make this even easier to use.<\/p>\n

As a result, we can deploy with more confidence, because we know that if something goes wrong, we can easily go back to the previous version.<\/p>\n","protected":false},"excerpt":{"rendered":"