alibaba/dubbo
Dubbo
Dubbo is a high-performance Java remote procedure call framework and microservice governance platform. It enables communication between distributed services using a remote service orchestrator and a distributed service registry to locate available providers in real time.
The system provides a microservice monitoring suite for health tracking and distributed tracing, alongside integrated security plugins for access control. It manages network traffic through routing strategies, rate limiting, and thread pool isolation to maintain system stability.
The framework covers broader capabilities in service discovery and microservice governance, allowing for the coordination of registration and configuration across distributed architectures.
Features
- Remote Procedure Call Frameworks - Provides a high-performance RPC framework for executing functions across distributed address spaces as if they were local calls.
- Service Discovery - Provides mechanisms for dynamically locating and routing to service instances via a distributed registry.
- Registry-Based Service Discovery - Locates available service providers by querying a centralized registry that synchronizes network addresses across the cluster.
- Network Traffic Management - Manages request flow using routing strategies, rate limiting, and thread pool isolation to maintain system stability.
- RPC Frameworks - Provides a high-performance Java RPC framework for communication between distributed services via TCP and REST.
- Service Exposure - Enables routing requests between distributed providers and consumers using high-performance TCP and REST protocols.
- Service Governance - Coordinates service discovery, registration, and load balancing to maintain stability in distributed microservices environments.
- Microservice Platforms - Serves as a comprehensive platform for governing service discovery, registration, and configuration in distributed architectures.
- Real-Time Push Updates - Implements real-time propagation of configuration changes from a central server to all connected application nodes.
- Dynamic Configuration Updates - The product supports updating application settings and environment variables in real-time without requiring a full restart of the service.
- Service Health Monitoring - Tracks operational health and performance of remote services through integrated metrics and distributed tracing.
- Real-time Configuration Updates - Enables updating environment variables and service settings in real time without needing to restart the application.
- Protocol-Agnostic Transport Layers - Decouples service APIs from network transport, allowing seamless switching between TCP, HTTP, and gRPC.
- Command-Based Pool Isolation - Protects system stability by allocating dedicated thread pools to different services to prevent cascading failures.
- Request Interceptors - Features a pluggable chain of filters to handle security, logging, and traffic routing for RPC requests.
- Proxy-Based Remote Invocation - Uses client-side dynamic proxies to transparently redirect local method calls to remote service providers.
- Traffic Orchestration Frameworks - Controls network traffic through routing strategies, rate limiting, and thread pool isolation.
- Microservices Health Monitoring - Ships a health tracking system providing distributed tracing and performance metrics for Java microservices.
- System Health Monitoring - Tracks application health and performance through integrated metrics, distributed tracing, and a management console.
- Distributed Applications - High-performance RPC framework for distributed services.
- Java and JVM Ecosystem - High-performance RPC framework for Java applications.
- Web Frameworks - High-performance Java RPC framework for distributed service governance.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
