| 失效链接处理 |
|
The Azure Cloud-Native Architecture Mapbook PDF 下载
本站整理下载：
相关截图：
主要内容：
Technical requirements
The Maps provided in this chapter are available at https://github.com/
PacktPublishing/The-Azure-Cloud-Native-Architecture-Mapbook/
tree/master/Chapter01 .
Getting to know architectural duties
Before we define what an Azure architect is, let's first define what an architect's role is
and how our maps specialize to reflect these different profiles. The word architect is used
everywhere on the IT planet. Many organizations have their own expectations when it
comes to defining the tasks and duties of an architect. Let's share our own definitions as
well as some illustrative diagrams.
Enterprise architects
Enterprise architects oversee the IT and business strategies, and they make sure that
every IT initiative is in line with the enterprise business goals. They are directly reporting
to the IT leadership and are sometimes scattered across business lines. They are also the
guardians of building coherent and consistent overall IT landscapes for their respective
companies. Given their broad role, enterprise architects have a helicopter view of the IT
landscape, and they are not directly dealing with deep-dive technical topics, nor are they
looking in detail at specific solutions or platforms, such as Azure, unless a company would
put all its assets in Azure. In terms of modeling, they often rely on the TOGAF (short for
The Open Group Architecture Framework) modeling framework and ArchiMate. The
typical type of diagrams they deal with looks like the following:
Figure 1.1 – Capability viewpoint: ArchiMate
As you can see, this is very high level and not directly related to any technology or
platform. Therefore, this book focusing on Azure is not intended for enterprise architects,
but they are, of course, still welcome to read it!
Getting to know architectural duties 5
Domain architects
Domain architects own a single domain, such as the cloud. In this case, the cloud is
broader than just Azure, as it would probably encompass both public and private cloud
providers. Domain architects are tech-savvy, and they define their domain roadmaps
while supervising domain-related initiatives. Compared to enterprise architects, their
scope is more limited, but it is still too broad to master the bits and bytes of an entire
domain. This book, and more particularly our generic maps, will certainly be of great
interest for cloud domain architects. Diagram-wise, the domain architects will also rely on
TOGAF and other architecture frameworks, but scoped to their domain.
Solution architects
Solution architects help different teams to build solutions. They have T-shaped skills,
which means that they are specialists in a given field (the base of the T), but they can also
collaborate across disciplines with the other experts (the top of the T). Solution architects
are usually in charge of designing solution diagrams, and they tackle non-functional
requirements, such as security, performance, and scalability. Their preferred readings
will be our chapter dedicated to solution architecture, as well as some reference
architectures. Solution architects may build both high-level technology-agnostic, and
platform-specific diagrams. Azure solution architects may build reference architectures,
such as, for instance, one that we can find on the Azure Architecture Center
( https://docs.microsoft.com/azure/architecture/ ):
|
苏公网安备 32061202001004号
