Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Azure Cloud Native Architecture Mapbook

You're reading from   The Azure Cloud Native Architecture Mapbook Explore Microsoft Cloud's infrastructure, application, data, and security architecture

Arrow left icon
Product type Paperback
Published in Feb 2021
Publisher Packt
ISBN-13 9781800562325
Length 376 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Stéphane Eyskens Stéphane Eyskens
Author Profile Icon Stéphane Eyskens
Stéphane Eyskens
Ed Price Ed Price
Author Profile Icon Ed Price
Ed Price
Ed Price Ed Price
Author Profile Icon Ed Price
Ed Price
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Section 1: Solution and Infrastructure
2. Chapter 1: Getting Started as an Azure Architect FREE CHAPTER 3. Chapter 2: Solution Architecture 4. Chapter 3: Infrastructure Design 5. Chapter 4: Infrastructure Deployment 6. Section 2: Application Development, Data, and Security
7. Chapter 5: Application Architecture 8. Chapter 6: Data Architecture 9. Chapter 7: Security Architecture 10. Section 3: Summary
11. Chapter 8: Summary and Industry Scenarios 12. Other Books You May Enjoy

Summary

In this chapter, we described the solution architecture map and its different classification categories, which are SoE, SoR, SoI, and systems of interaction (IPaaS). This categorization, commonly used in architecture, makes it easier to dispatch services. We provided explanations and extra-focused maps, which helped further refine the alternatives.

We also emphasized the importance of cross-cutting concerns that apply to every solution, and we discussed which concerns should be considered by solution architects. Remember that it might be too challenging to address all of the concerns on day one of your cloud journey. It is, therefore, interesting to think of different maturity levels, and how we would put them on a roadmap to manage our stakeholders' expectations.

Next, we highlighted the containerization components, with a focused map that depicted the container landscape of Azure. We also considered other dimensions, such as cost, complexity, and the level of residual...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime