Book Image

Architecting Cloud Native Applications

By : Kamal Arora, Erik Farr, John Gilbert, Piyum Zonooz
Book Image

Architecting Cloud Native Applications

By: Kamal Arora, Erik Farr, John Gilbert, Piyum Zonooz

Overview of this book

Cloud computing has proven to be the most revolutionary IT development since virtualization. Cloud native architectures give you the benefit of more flexibility over legacy systems. This Learning Path teaches you everything you need to know for designing industry-grade cloud applications and efficiently migrating your business to the cloud. It begins by exploring the basic patterns that turn your database inside out to achieve massive scalability. You’ll learn how to develop cloud native architectures using microservices and serverless computing as your design principles. Then, you’ll explore ways to continuously deliver production code by implementing continuous observability in production. In the concluding chapters, you’ll learn about various public cloud architectures ranging from AWS and Azure to the Google Cloud Platform, and understand the future trends and expectations of cloud providers. By the end of this Learning Path, you’ll have learned the techniques to adopt cloud native architectures that meet your business requirements. This Learning Path includes content from the following Packt products: • Cloud Native Development Patterns and Best Practices by John Gilbert • Cloud Native Architectures by Erik Farr et al.
Table of Contents (24 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Decoupling deployment from release


Let's start this chapter by posing three questions:

  1. Did you notice that the Deployment chapter is before the Testing chapter?
  2. Do you find the typical definitions of continuous delivery versus continuous deployment unsatisfying?
  3. How can a company possibly perform multiple deployments each day and still have any confidence that the system will continue to function properly?

I placed the Deployment chapter before the Testing chapter to emphasize the fact that we are shifting the activity of deployment all the way to the left on the life cycle timeline of any given bounded isolated component. In fact, I advocate deploying a new component all the way into production on the very first day of its development. This first deployment is just a boilerplate stub created from a well-crafted template or it may even be just an empty stack. Regardless, the goal of this first task is to get the plumbing of the deployment pipeline up and running as the first order of business...