官术网_书友最值得收藏!

Microservices and orchestration

As we break down an application into very specific domains, we need a uniform way to communicate between all the various pieces and domains. Web services have served this purpose for years, but the added isolation and granular focus that containers bring have paved a way for microservices.

The definition for microservices can be a bit nebulous, but a definition from Martin Fowler, a respected author and speaker on software development, says this (you can refer to more details about this in point 2 in the References section at the end of the chapter):

In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.

As the pivot to containerization and as microservices evolve in an organization, they will soon need a strategy to maintain many containers and microservices. Some organizations will have hundreds or even thousands of containers running in the years ahead.

主站蜘蛛池模板: 江津市| 宜城市| 宝丰县| 巴青县| 沾益县| 衡水市| 长宁区| 万年县| 福安市| 荣昌县| 青岛市| 通河县| 府谷县| 茂名市| 邵阳县| 景德镇市| 安化县| 汝州市| 华坪县| 潮州市| 连山| 平顶山市| 怀远县| 平湖市| 哈密市| 海口市| 汤原县| 昌吉市| 临汾市| 会泽县| 承德市| 祁门县| 麻栗坡县| 思南县| 板桥市| 土默特右旗| 行唐县| 宾川县| 迁安市| 凤城市| 林口县|