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

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.

主站蜘蛛池模板: 大足县| 明溪县| 福州市| 金秀| 鸡东县| 马龙县| 班戈县| 桃园市| 布尔津县| 常州市| 武义县| 合肥市| 吉隆县| 湟源县| 襄汾县| 沙湾县| 泸溪县| 闵行区| 青铜峡市| 南和县| 隆子县| 远安县| 霍州市| 永昌县| 浮梁县| 元氏县| 邛崃市| 呼伦贝尔市| 名山县| 宁夏| 沙田区| 外汇| 合山市| 松江区| 儋州市| 丰原市| 怀远县| 桑日县| 沈阳市| 金湖县| 舒城县|