- Getting Started with Kubernetes
- Jonathan Baier Jesse White
- 191字
- 2021-06-10 19:46:57
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 the way for microservices.
A definition for microservices can be a bit nebulous, but a definition from Martin Fowler, a respected author and speaker on software development, says this:
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.
推薦閱讀
- Circos Data Visualization How-to
- JMAG電機電磁仿真分析與實例解析
- Cloudera Administration Handbook
- Ceph：Designing and Implementing Scalable Storage Systems
- C語言寶典
- Azure PowerShell Quick Start Guide
- 電腦日常使用與維護322問
- 學練一本通：51單片機應用技術
- 基于敏捷開發的數據結構研究
- 嵌入式Linux系統實用開發
- WOW！Photoshop CS6完全自學寶典
- Building Google Cloud Platform Solutions
- 手把手教你學Flash CS3
- 玩機器人 學單片機
- Serverless Design Patterns and Best Practices