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

The essence of DevOps

DevOps is not a new paradigm; however, it's gaining a lot of popularity and traction. Its adoption is at its highest level, and more and more companies are undertaking this journey. I purposely mentioned DevOps as a journey because there are different levels of maturity within DevOps. While successfully implementing continuous deployment and delivery are considered the highest level of maturity in this journey, adopting source code control and Agile software development are considered the first step in the DevOps journey.

One of the first things DevOps talks about is breaking down the barriers between the development and the operations teams. It brings about close collaboration between multiple teams. It's about breaking the mindset that the developer is responsible for writing the code only and passing it on to operations for deployment once it's tested. It's also about breaking the mindset that operations have no role to play in development...