Chapter 5. Using DNS in Your DevOps Approach

We have discussed the benefits of DNS and DevOps independently, now let’s drill down into some more detail about how DNS can be employed specifically when implementing a DevOps culture.

For all of these there are alternative ways to deliver the same results, but the built-in fault tolerance and independence from your other infrastructure mean that it is worth considering using DNS.

Use DNS to Streamline Deployment Pipelines

One of the primary objectives in moving to a DevOps culture is to increase the the cadence of deployments to production, ideally moving much closer to a Continuous Delivery system.

Continuous Delivery

Continuous Delivery is a term coined to refer to the objective of an Agile development system to ensure that changes would always be ready to go to production after completion. Originally coined to mean continually deliverable, it has been adopted within the DevOps world to refer to the practice of being so confident in the automated validation and deployment pipeline that any changes get pushed directly to production without any human intervention.

This speed of deployment involves several changes:

  • Trust in the validity of automation of the testing and deployment process
  • Repeatability of the deployment process
  • Reliable way of validating success of deployment
  • Simple and reliable rollback process

There are several ways that DNS can be employed to deliver these objectives.

Blue/Green Deployment

Traditionally, deployment ...

Get DevOps and DNS now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.