Book Image

Cloud Native Architectures

By : Tom Laszewski, Kamal Arora, Erik Farr, Piyum Zonooz
Book Image

Cloud Native Architectures

By: Tom Laszewski, Kamal Arora, Erik Farr, 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. To harness this, businesses need to refresh their development models and architectures when they find they don’t port to the cloud. Cloud Native Architectures demonstrates three essential components of deploying modern cloud native architectures: organizational transformation, deployment modernization, and cloud native architecture patterns. This book starts with a quick introduction to cloud native architectures that are used as a base to define and explain what cloud native architecture is and is not. You will learn what a cloud adoption framework looks like and develop cloud native architectures using microservices and serverless computing as design principles. You’ll then explore the major pillars of cloud native design including scalability, cost optimization, security, and ways to achieve operational excellence. In the concluding chapters, you will also learn about various public cloud architectures ranging from AWS and Azure to the Google Cloud Platform. By the end of this book, you will have learned the techniques to adopt cloud native architectures that meet your business requirements. You will also understand the future trends and expectations of cloud providers.
Table of Contents (19 chapters)
Title Page
Packt Upsell
Foreword
Contributors
Preface
Index

Patterns for moving from monolithic application architectures to Azure native architectures


Although cloud migrations have common patterns and methodologies, every cloud provider brings in a different flavor to it with their services and overall messaging. So, like we discussed earlier, AWS has a 6Rs migration methodology, but when it comes to Azure's methodology, it's pretty simplistic. As per https://azure.microsoft.com/en-us/migration/, it mainly categorizes migration into three parts:

  • Discover: In this phase, you assess the current state of virtual machines, databases, and applications in an on-premises environment and evaluate their migration path and priority.
  • Migrate: This is the actual process of moving your applications, databases, and VMs to the Azure cloud by using cloud native or third-party tools, which help you transfer the bits by means of replication.
  • Optimize: Once your applications and data is in the Azure cloud, you can further fine-tune for costs, performance, security,...