- The DevOps 2.1 Toolkit:Docker Swarm
- Viktor Farcic
- 164字
- 2021-07-09 21:03:40
Service Discovery inside a Swarm Cluster
It does not take much strength to do things, but it requires a great deal of strength to decide what to do.
-Elbert Hubbard
-Elbert Hubbard
If you used the old Swarm, the one shipped as a standalone product before Docker 1.12, you were forced to set up a service registry alongside it. You might have chosen Consul, etcd, or Zookeper. The standalone Swarm could not work without one of them. Why is that? What was the reason for such a strong dependency?
Before we discuss reasons behind using an external service registry with the old Swarm, let's discuss how would Swarm behave without it.
推薦閱讀
- TestStand工業自動化測試管理(典藏版)
- INSTANT Varnish Cache How-to
- JSF2和RichFaces4使用指南
- 運動控制器與交流伺服系統的調試和應用
- Cloudera Administration Handbook
- 基于32位ColdFire構建嵌入式系統
- 基于單片機的嵌入式工程開發詳解
- R Data Analysis Projects
- 工業機器人集成應用
- 步步驚“芯”
- MongoDB 4 Quick Start Guide
- 機器人制作入門(第4版)
- 樂高創意機器人教程(中級 上冊 10~16歲) (青少年iCAN+創新創意實踐指導叢書)
- 中小型網站建設與管理
- 多傳感器數據智能融合理論與應用