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

Chapter 10. Microsoft Azure

Microsoft Azure had a very different start compared to AWS. It was originally launched in 2009 as the Windows Azure platform, where the focus was on developers and Platform-as-a-Service (PaaS) components. The initial set of services that were launched were Windows Server AppFabric and ASP.NET MVC2 to help developers build applications using the frameworks and services in the cloud. The only infrastructure components at that time were Windows Server virtual machines to enable hybrid use cases, but the overall strategy was still geared towards developer community, which was radically different from AWS, who had more infrastructure components around that time being offered apart from some basic application-centric services. With this foray into the cloud, Azure continued the push towards application aspects until 2014, when it changed the whole strategy to go into the IaaS space as well and also rebranded the platform to Microsoft Azure.


Refer to this first blog...