1 views collected around this technical thread.
This article explains the principles and workflow of Nacos service registration, covering why dynamic service discovery is needed, how instances register, send heartbeats, and are deregistered, and includes code examples and diagrams to illustrate the process.
This article explains the fundamentals and implementation of a Nacos service registry in a Spring Cloud microservice architecture, covering registration concepts, building a standalone Nacos server, creating provider and consumer services, and deep-diving into the underlying registration code and HTTP interactions.
This article explains why Dubbo transitioned from interface-level to application-level service registration in version 3.x, detailing the performance pressures of interface registration, alignment with Spring Cloud and Kubernetes, and the underlying implementation using metadata centers, Nacos, Redis, and Zookeeper.
This article explains the underlying principles of Nacos as a service registry, covering registration flow, health‑checking, dynamic service awareness, the architecture diagram, key source‑code components, and how service discovery works in Spring Cloud micro‑service environments.
This article explains the origins of service registration and discovery in microservice architectures, outlines the core problems they solve, describes their key characteristics, and compares implementation approaches such as DNS, Zookeeper, Dubbo, and Eureka, highlighting the differences between Zookeeper and Eureka through the CAP theorem.
This guide walks through installing and using Spring Cloud Tencent with Polaris, covering environment setup, Polaris deployment, Spring Boot project configuration, service registration, configuration center integration, rate‑limiting, circuit‑breaker features, and metadata transfer, while highlighting common pitfalls and practical code examples.
This article explains the evolution from monolithic to microservice architectures, compares their advantages and disadvantages, and details essential components such as service gateways, service registration and discovery mechanisms, and distributed configuration centers, while also reviewing popular open‑source solutions.
The article presents a Spring Cloud micro‑service solution that combines pluggable warm‑up modules and delayed deregistration to ensure graceful startup and shutdown, preventing premature object destruction, late offline calls, and early registration, thereby achieving over 99.99 % deployment success and stable request latency.
This article explains the differences between monolithic and microservice architectures, outlines their advantages and disadvantages, and then dives into essential components such as service gateways, service registration and discovery, and distributed configuration centers, providing practical guidance for building scalable backend systems.
This article provides a detailed analysis of Nacos as a service registry, covering its architecture, registration and discovery processes, health‑checking, Raft‑based consistency, Spring Cloud integration, and practical code examples for developers building micro‑service systems.
This article explains how service registration centers decouple providers and consumers in microservice architectures, discusses the CAP theorem trade‑offs, categorizes registration approaches, and compares popular solutions such as Eureka, Consul, Nacos, CoreDNS, and ZooKeeper across key features and integration aspects.
This article explains the concepts, architecture, and workflow of service registration and discovery in microservice systems, outlines the roles of providers, consumers, and registries, and compares popular registration centers such as Eureka, ZooKeeper, and Consul to help you choose the right solution for your environment.
This article explains the internal architecture of Nacos, its role as a service registry in Spring Cloud, the registration and heartbeat mechanisms, and how clients dynamically discover service instances using both Open API and SDK approaches.
Youzan’s service registration and discovery architecture progressed from fine‑grained interface‑level registration on Etcd, through an intermediate application‑level discovery layer using Istio Pilot and the Tether sidecar, to a fully application‑level, sidecar‑driven model with CRD metadata, enabling scalable, cloud‑native multi‑region service mesh.
The article compares four popular service registration centers—Eureka, Zookeeper, Consul, and Nacos—by outlining each system’s architecture, core principles, and operational mechanisms, with an in‑depth source‑code‑level examination of Nacos’s pull/push discovery, Raft‑based leader election, and concurrent instance management, and concludes with a comparative table of consistency, availability, and partition‑tolerance characteristics.
This article provides a comprehensive overview of microservice architecture, covering the definition, typical components, prerequisites for service‑orientation, methods for publishing and referencing services, registration and discovery mechanisms, remote communication, and detailed strategies for ensuring stability of registration centers, service consumers, and service providers.
This article explains the origins of service registration and discovery in microservice architectures, outlines the problems they address, describes their key characteristics, and compares implementation approaches such as DNS, Zookeeper, Dubbo, and Eureka, highlighting the CAP‑theorem trade‑offs between Zookeeper (CP) and Eureka (AP).
This article explains how to describe, publish, register, discover, invoke, monitor, trace, and govern RPC services in a microservice architecture, covering RESTful API, XML configuration, IDL files, registry principles, Zookeeper deployment, connection methods, server processing models, monitoring metrics, tracing concepts, and common governance techniques such as load balancing and fault tolerance.
The article examines the pressures on Toutiao's architecture, outlines its three-stage evolution from a simple three‑tier system to a split architecture and finally microservices, and details the service‑registration, authorization, and custom RPC framework that enable rapid, reliable backend development.