This article explains the role of a microservice registration center, its core principles and workflow, and compares popular frameworks such as Eureka, Nacos, Zookeeper, and Consul to help you select the most suitable solution for your architecture.
This article explains the importance of service discovery in high‑availability systems, compares DNS, VIP, Zookeeper‑based CP solutions and message‑bus‑based AP approaches, outlines their registration and subscription workflows, highlights scalability and consistency trade‑offs, and provides practical guidance for designing robust registration centers.
This article explains how to replace the default Swagger‑UI with Knife4j, outlines the problems of using Swagger in a microservice environment, and presents two documentation aggregation patterns—gateway aggregation and a centralized registration mode—detailing the architecture, database schema, and Spring Boot starter implementation for a reusable Swagger registration server.
This article examines why ZooKeeper may not be the optimal solution for service discovery, analyzing CAP trade‑offs, consistency versus availability, scalability limits, health‑check design, and practical lessons from Alibaba’s decade‑long experience to guide the design of robust registration centers.
The article analyzes the evolution of service registration in Alibaba, compares ZooKeeper with other solutions, and argues that for large‑scale service discovery a registration center should prioritize availability over strong consistency, support flexible health checks, handle partitions gracefully, and avoid the pitfalls of using ZooKeeper as a universal registry.
The article analyzes the limitations of using ZooKeeper for service discovery, compares it with Alibaba's ConfigServer, discusses CAP trade‑offs, scalability, health‑check design, disaster recovery, and provides practical guidance on when to choose alternative registration solutions.
This article examines a decade of Alibaba’s experience with ZooKeeper‑based service discovery, arguing that ZooKeeper’s strong consistency and limited scalability make it unsuitable as a registration center and outlining design principles that favor availability, eventual consistency, and richer health‑check mechanisms.
Drawing on Alibaba's decade‑long experience, this article analyses service‑discovery requirements, CAP trade‑offs, consistency versus availability, health‑check design, disaster recovery, and exception handling to argue that ZooKeeper, while excellent for coordination, is often unsuitable as the primary registration center for large‑scale microservice environments.
This article analyzes the limitations of ZooKeeper for service discovery, covering consistency, partition tolerance, scalability, persistence, health‑checking, disaster‑recovery, and operational complexities, and explains why modern registration centers should favor AP designs and richer health‑check mechanisms.
Based on a decade of Alibaba’s production experience, this article analyzes the requirements and design trade‑offs of service‑discovery registries, arguing that ZooKeeper’s strong consistency and coordination focus make it unsuitable as a primary registration center and proposing AP‑oriented, scalable alternatives.
This article provides a comprehensive analysis of mainstream microservice service‑registry products—including Nacos, Eureka, ZooKeeper, and Consul—covering their data models, consistency protocols, load‑balancing strategies, health‑check mechanisms, performance, scalability, usability, and extensibility to guide practitioners in selecting and designing registration centers.
This article details NetEase Kaola’s journey from a monolithic Java backend to a micro‑service architecture powered by Dubbo, covering service decomposition, circuit breaking, rate limiting, comprehensive monitoring, API gateway, multi‑language support, registration‑center redesign, and future plans for dual‑data‑center deployment and service‑mesh adoption.
