Moving to the cloud is a natural evolution of focusing on software, and cloud-native application architectures are at the center of how these companies obtained their disruptive character. By cloud, we mean any computing environment in which computing, networking, and storage resources can be provisioned and released elastically in an on-demand, self-service manner. This definition includes both public cloud infrastructure (such as Amazon Web Services, Google Cloud, or Microsoft Azure) and private cloud infrastructure (such as VMware vSphere or OpenStack).
In 1st chapter we’ll explain how cloud-native application architectures enable these innovative characteristics. Then we’ll examine a few key aspects of cloud-native application architectures.A great deal of the changes necessary for enterprise IT shops to adopt cloud-native architectures will not be technical at all. They will be cultural and organizational changes that revolve around eliminating structures, processes, and activities that create waste. In this section we’ll examine the necessary cultural shifts.In 3rd section we’ll walk step-by-step through a series of recipes that provide a process for decomposing monolithic services and moving them to the cloud.


Adoption of cloud-native application architectures is helping many organizations transform their IT into a force for true agility in the marketplace. This O’Reilly report defines the unique characteristics of cloud-native application architectures such as microservices and twelve-factor applications.

Author Matt Stine also examines the cultural, organizational, and technical changes necessary to migrate traditional monolithic applications and service-oriented architectures to cloud-native architectures. You’ll also find a Migration Cookbook, with recipes for decomposing monolithic applications into microservices, implementing fault-tolerant patterns, and performing automated testing of cloud-native services.

This report discusses application architectures that include:
• The Twelve-Factor App: a collection of cloud-native app architecture patterns
• Microservices: independently deployable services that do one thing well
• Self-Service Agile Infrastructure: platforms for rapid, repeatable, and consistent provisioning of app environments and backing services
• API-based Collaboration: published and versioned APIs that allow interaction between services in a cloud-native app architecture

• Anti-Fragility: systems that get stronger when subjected to stress

迁移到云端是专注于软件的自然演变，而云原生应用程序架构是这些公司如何获得其破坏性特征的中心。所谓云，我们指的是任何计算环境，其中的计算、网络和存储资源可以以按需、自助的方式弹性地配置和释放。这个定义包括公共云基础设施（如亚马逊网络服务，谷歌云，或微软Azure）和私人云基础设施（如VMware vSphere或OpenStack）。

在第1章中，我们将解释云原生应用架构是如何实现这些创新特征的。然后，我们将研究云原生应用架构的几个关键方面。企业IT部门采用云原生架构所需的大量变化根本不是技术上的。它们将是文化和组织的变化，围绕着消除造成浪费的结构、流程和活动。在本节中，我们将研究必要的文化转变。在第三节中，我们将逐步完成一系列的配方，提供一个分解单体服务并将其转移到云中的过程。

采用云原生应用架构正在帮助许多组织将他们的IT转变为市场中真正的敏捷性力量。这份O'Reilly报告定义了云原生应用架构的独特特征，如微服务和十二要素应用。

作者Matt Stine还研究了将传统的单体应用和面向服务的架构迁移到云原生架构所需的文化、组织和技术变化。你还会发现一本《迁移食谱》，其中有将单体应用分解为微服务、实现容错模式以及对云原生服务进行自动测试的食谱。