1 views collected around this technical thread.
This guide explains how to build a Nacos service cluster, configure providers and consumers, write the necessary Spring Cloud Nacos YAML and Java controller code, detail the steps for setting up multiple Nacos nodes, and troubleshoot typical startup errors.
This article outlines a step‑by‑step solution for exposing pod domain names inside a corporate network using CoreDNS with an etcd backend, including server and agent deployment, configuration, verification, and practical usage recommendations.
This article examines Nacos 3.0’s major architectural overhaul—including console‑service decoupling, independent ports, three deployment modes, a new bootstrap startup engine, and step‑by‑step embedded integration—showcasing how the redesign boosts security, performance, and flexibility for microservice ecosystems.
The article introduces Nacos 3.0’s major upgrades—including migration to JDK 17 and Spring Boot 3.4.1, new Admin APIs, default authentication, AI‑focused Model Content Protocol, distributed lock, fuzzy listening, and native xDS support—while also promoting an enterprise‑level backend engineering booklet priced at 11.9 CNY.
Version 3.0 of Nacos introduces major updates—including JDK 17 and Spring Boot 3.4.1 support, enhanced Admin and Console APIs, default authentication, AI‑focused Model Content Protocol, unified namespaces, beta distributed lock and fuzzy listening features, and native xDS protocol support—aimed at improving cloud‑native service discovery and configuration management.
Nacos 3.0 introduces major upgrades—including JDK 17 and Spring Boot 3.4.1 support, a new Admin API, default authentication, AI‑focused MCP, unified namespaces, beta distributed lock and fuzzy listening features, plus native xDS protocol support—positioning it as a powerful cloud‑native service discovery and configuration platform.
This article describes how to build a lightweight service registry using Eureka Server that also acts as a client, enabling a task dispatcher to discover and load‑balance task executor instances without deploying a separate registry, including Maven dependencies, Spring annotations, Feign client definitions, and troubleshooting steps.
This article explains common Kubernetes DNS resolution failures, both for external domains and internal service discovery addresses, and provides a step‑by‑step troubleshooting workflow that includes checking CoreDNS, examining resolv.conf, adjusting DNS settings, and recreating CoreDNS when necessary.
This guide explains common Kubernetes DNS problems—including failure to resolve external domains, inter‑pod service discovery addresses, and related impacts on applications like Nginx reverse proxies—and provides step‑by‑step troubleshooting procedures such as checking CoreDNS, inspecting resolv.conf, and customizing dnsPolicy and dnsConfig in pod specifications.
This guide explains how to use Spring Cloud Alibaba Sidecar to integrate heterogeneous microservices, covering its principles, configuration, health‑check setup, and a complete hands‑on example with Spring Boot services, Sidecar registration, Nacos discovery, and RestTemplate calls, while guaranteeing permanent updates for subscribers.
Learn how to deploy a highly available Nacos service on Kubernetes using PostgreSQL as the backend, covering prerequisites, database initialization, configuration, Helm‑free manifests, driver installation, and verification steps to build a reliable micro‑service platform.
This article explores the fundamentals of load balancing in microservice architectures, detailing both stateless and stateful strategies such as round‑robin, random, hash, and weighted algorithms, and demonstrates how go‑zero and gRPC implement these mechanisms through custom balancers, service discovery, and request scheduling.
This article explores the fundamentals of distributed systems, compares stateful and stateless services, examines monolithic, SOA, and microservice models, and provides practical guidance on access layers, fault tolerance, service discovery, scaling, and data storage for building robust cloud‑native architectures.
This article compares Dubbo and Feign, outlining their architectures, features, and suitability for different microservice scenarios, and provides practical guidance on selecting the appropriate RPC framework based on performance, reliability, and development efficiency requirements.
The new Rainbow Bridge architecture replaces the SLB‑based load‑balancing model with a self‑managed, multi‑AZ metadata center and enhanced SDK that aggregates node health, provides zone‑aware weighted routing, supports rapid failover and manual overrides, and delivers faster recovery and scalable traffic handling.
This article walks through building a lightweight service registry using Eureka Server and Client to enable task distribution and execution, covering requirements, integration steps, code examples, load balancing, and troubleshooting, while avoiding separate deployment of a full registration center.
This article explains Nacos, Alibaba's dynamic naming and configuration service, covering its architecture, service registration and discovery mechanisms, Raft‑based consistency, and configuration management with long‑polling, providing a comprehensive overview for microservice practitioners.
The article diagnoses a 2023 Dubbo outage caused by Zookeeper’s jute.maxbuffer limit being exceeded by millions of temporary nodes, explains why Zookeeper’s CP model is ill‑suited for service registries, and outlines an automated migration to Spring Cloud using generated REST controllers and proxies that achieve comparable performance, especially for larger payloads.
This article explains the evolution from monolithic to microservice architectures, introduces Spring Cloud Alibaba and Nacos for service discovery and governance, provides step‑by‑step installation and configuration instructions, and demonstrates load balancing with Ribbon, including essential code snippets for quick adoption.
Zookeeper, the open‑source coordination service modeled after Google’s Chubby, offers strong consistency for distributed applications, but its CP design, synchronous master‑slave replication, log‑heavy state changes, and limited health checks lead many large tech firms to favor more available alternatives, though it still fits certain use cases.