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

Chapter 15. 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.

Note

Refer to this first blog...