You're reading from Azure for Architects Create secure, scalable, high-availability applications on the cloud

Product type Paperback

Published in Jul 2020

Publisher Packt

ISBN-13 9781839215865

Length 698 pages

Edition 3rd Edition

Languages

ActionScript

Tools

Azure

Concepts

Cloud Computing

Authors (3):

Jack Lee

Ritesh Modi

Rithin Skaria

View More author details

Table of Contents (21) Chapters

Preface

About Azure for Architects, Third Edition

1. Getting started with Azure

2. Azure solution availability, scalability, and monitoring FREE CHAPTER

3. Design pattern – Networks, storage, messaging, and events

4. Automating architecture on Azure

5. Designing policies, locks, and tags for Azure deployments

6. Cost management for Azure solutions

7. Azure OLTP solutions

8. Architecting secure applications on Azure

9. Azure Big Data solutions

10. Serverless in Azure – Working with Azure Functions

11. Azure solutions using Azure Logic Apps, Event Grid, and Functions

12. Azure Big Data eventing solutions

13. Integrating Azure DevOps

14. Architecting Azure Kubernetes solutions

15. Cross-subscription deployments using ARM templates

16. ARM template modular design and implementation

17. Designing IoT solutions

18. Azure Synapse Analytics for architects

19. Architecting intelligent solutions

Index

DevOps with containers

In a typical architecture, container runtimes are deployed on virtual machines and containers are run within them. The typical architecture for IaaS container-based solutions is shown here:

IaaS container-based solution architecture

Figure 13.18: Architecture for IaaS container-based solutions

These containers are managed by container orchestrators such as Kubernetes. Monitoring services are provided by Log Analytics and all secrets and keys are stored in Azure Key Vault. There is also a pull server, which could be on a virtual machine or Azure Automation, providing configuration information to the virtual machines.

Containers

Containers are a virtualization technology; however, they don't virtualize physical servers. Instead, containers are an operating system-level virtualization. This means that containers share the operating system kernel provided by their host among themselves and with the host. Running multiple containers on a host (physical...