第七章 基线云架构
Cloud transitions can be difficult to begin. As discussed in , Architecting for Transition, transitions can be difficult to design and plan, as much of the diligence now falls on the consumer side. This change is a double-edged sword; it cuts both ways. It enables the consumer to have significantly more control over designs, technical choices, economics, and risk. It also places the significantly more of the design and architecture burden on the consumer, who may not have the level of solution design experience that many service providers do.
Baseline cloud architectures are foundational building blocks to cornerstone design ideas. These common design arrangements can be used to jump-start solution efforts. Baseline architectures are useful when leveraging standard cloud computing patterns. Patterns represent cloud service requirements, while baseline architectures provide useful models for handling common architectural components and their associated requirements.
Each of the following sections will build on the section previous. The baseline compute component takes into account a web layer, application layer, and database layer, each having some level of storage. Storage attributes will change based on design requirements. Nearly all modern designs will have web, app, and database layers in their designs.
This type of layering is called tiering. Most designs will have three or four tiers. Tiers are typically the number of individual isolated layers between the environment entry point and the destination data. As an example, a three-tier architecture has a web layer, app layer, and database layer. A single-server architecture will have all three layers residing on the same virtual or physical server.
In this chapter, we will cover the following topics:
Baseline architecture types
OSI model and layer description
Complex architecture types
Architecting for hybrid clouds