Book Image

Azure for Architects

Book Image

Azure for Architects

Overview of this book

Over the years, Azure cloud services has grown quickly, and the number of organizations adopting Azure for their cloud services is also gradually increasing. Leading industry giants are finding that Azure fulfills their extensive cloud requirements. This book will guide you through all the important and tough decision-making aspects involved in architecturing a Azure public cloud for your organization. The book starts with an extensive introduction to all the categories of designs available with Azure. These design patterns focus on different aspects of cloud such as high availability, data management, and so on. Gradually, we move on to various aspects such as building your cloud structure and architecture. It will also include a brief description about different types of services provided by Azure, such as Azure functions and Azure Analytics, which can prove beneficial for an organization. This book will cover each and every aspect and function required to develop a Azure cloud based on your organizational requirements. By the end of this book, you will be in a position to develop a full-fledged Azure cloud.
Table of Contents (13 chapters)

A short history of serverless

Before we understand serverless, its architecture, and implementation, it is important to understand its history and how it evolved.

At the beginning there were physical servers. Although users had complete control over physical servers, there were lots of disadvantages:

  • Long gestation period between ordering and actual deployment of the server
  • Capital intensive in nature
  • Waste of resources
  • Lower return on investment
  • Difficult to scale out and up

A natural evolution to physical servers was virtualization. Virtualization refers to the creation of virtual machines on top of physical servers and deploying applications within them. Virtual machines provide advantages in terms of the following:

  • No need to procure physical hardware
  • Comparatively easier to create newer virtual machines
  • Complete isolation of environments
  • Lower costs compared to physical...