Understanding Dubbo's Layered Architecture and Core Components

Dubbo is Alibaba's open‑source distributed service framework that adopts a layered architecture to achieve loose coupling between components. It distinguishes two primary roles: the service provider (Provider) and the service consumer (Consumer), each interacting through a well‑defined service model.

The overall architecture consists of ten layers, with the topmost Service layer exposing business interfaces for developers. The diagram (not shown) highlights consumer‑side interfaces in light blue, provider‑side interfaces in light green, and shared interfaces along the central axis.

Key layers include:

Service Layer : Defines business interfaces and implementations.

Config Layer : Manages external configuration via ServiceConfig and ReferenceConfig, usable directly or through Spring.

Proxy Layer : Provides transparent client‑side stubs and server‑side skeletons, centered on ServiceProxy.

Registry Layer : Handles service address registration and discovery, abstracted by RegistryFactory, Registry, and RegistryService.

Cluster Layer : Implements routing, load balancing, and aggregates multiple providers into a single logical invoker.

Monitor Layer : Tracks RPC call counts and latency via Statistics, MonitorFactory, and related interfaces.

Protocol Layer : Core RPC entry point managing Invoker lifecycle; includes various protocols such as Dubbo, Hessian, HTTP, RMI, WebService, Thrift, Memcached, and Redis.

Exchange Layer : Wraps request‑response semantics, converting synchronous calls to asynchronous.

Transport Layer : Abstracts network transports (e.g., Mina, Netty, Grizzly) via Message‑centric interfaces.

Serialize Layer : Provides serialization utilities via Serialization, ObjectInput, ObjectOutput, and ThreadPool.

Dubbo's core concepts include service definition, registration (with registries like Zookeeper, Multicast, Redis, Simple), monitoring, and remote communication using protocols such as Mina, Netty, and Grizzly.

The framework’s Maven modules reflect this structure: dubbo-common (utilities and models), dubbo-remoting (protocol implementations), dubbo-rpc (abstract RPC handling), dubbo-cluster (load balancing and fault tolerance), dubbo-registry (registry abstractions), dubbo-monitor (metrics), dubbo-config (public API), and dubbo-container (standalone container).

Overall, Dubbo provides a comprehensive ecosystem for building scalable, high‑performance backend services through its modular, layered design.