1 What’s CI/CD?
This chapter covers
- The path organizations have taken to evolve from monolith applications to cloud-native applications
- The challenges organizations are facing when implementing CI/CD practices for cloud-native architectures
- An overview of continuous integration, deployment, and delivery practices
- How CI/CD tools like Jenkins can bring business value to organizations who undertake the journey of continuous everything
Software development and operations have experienced several paradigm shifts recently. These shifts have presented the industry with innovative approaches for building and deploying applications. More importantly, two significant paradigm shifts have consolidated their capabilities for developing, deploying, and managing scalable applications: DevOps and the cloud-native architecture.
Cloud-native architecture emerged with cloud adoption, with cloud providers like Amazon Web Services (AWS), Google Cloud Platform (GCP), or Microsoft Azure taking ownership of the infrastructure. Open-source tools like Kubernetes, Docker, or Istio offer horizontal scaling ability, letting developers build and run modern scalable applications without worrying about the underlying infrastructure. As a result, operational overhead is reduced and the development velocity of applications is increased.
DevOps bridged the divide between developers and ops teams and brought back harmony through collaboration, automated tools, and iterative and agile development and deployment.