Snailclimb/guide-rpc-framework
Guide Rpc Framework
This is a remote procedure call framework built on Netty for asynchronous communication between distributed services. It provides the infrastructure necessary to execute remote procedure calls across a network, allowing clients and servers to interact without blocking.
The framework utilizes Zookeeper for service registration and dynamic discovery, ensuring that service providers can be located automatically at runtime. It includes a service versioning manager to organize and track different iterations of service interfaces, enabling side-by-side deployments of multiple versions.
The system implements binary serialization via Kryo to convert Java objects into compact byte streams for network transport. It also incorporates a distributed load balancer that routes requests across providers using random or round-robin strategies, and uses heartbeat-based monitoring to track service availability and connection health.
Features
- Remote Procedure Calls - Provides a high-performance framework for executing remote procedures as if they were local function calls.
- Complex Data Serialization - Serializes complex Java objects into efficient byte streams for fast transmission over the network.
- Data Serialization Formats - Implements binary serialization formats to move Java objects efficiently across the network.
- Serialization Libraries - Utilizes the Kryo library for converting Java objects into binary formats for network transport.
- Service Instance Registrations - Utilizes Zookeeper to announce service provider locations and enable dynamic discovery during runtime.
- Binary Serialization - Employs Kryo to convert complex Java objects into compact binary streams for efficient network transmission.
- Netty-Based Servers - Leverages Netty's event-driven non-blocking I/O model for high-concurrency request and response processing.
- RPC Frameworks - Provides a high-performance RPC framework built on Netty for asynchronous distributed communication.
- Traffic Distribution - Distributes RPC requests across multiple available providers using random or round-robin selection strategies.
- Dynamic Service Discovery - Provides mechanisms for locating available service provider instances via a centralized Zookeeper registry.
- Service Discovery Registries - Uses Zookeeper to maintain a dynamic registry of service providers for automatic runtime discovery.
- Registry Heartbeat Monitoring - Uses periodic heartbeat signals to track service availability and evict unresponsive nodes from the registry.
- Proxy-Based Remote Invocation - Utilizes dynamic proxies and Java reflection to transparently route local method calls to remote servers.
- Distributed Load Balancing - Routes RPC requests across a distributed pool of providers to optimize resource utilization.
- Load Balancing Strategies - Distributes incoming RPC requests across available providers using random and round-robin selection strategies.
- Interface Versioning - Organizes and tracks different versions of service interfaces to allow side-by-side deployments.
- Service Version Management - Manages multiple iterations of service interfaces to enable side-by-side deployments of different versions.
- Load Balancers - Balances network traffic across multiple service instances using random or round-robin rotation.
- Asynchronous Service Invocations - Implements non-blocking remote calls that return futures to enable asynchronous processing.
- Service Versioning Strategies - Provides a service versioning manager to organize and track different iterations of service interfaces for side-by-side deployment.
- RPC Connection Heartbeats - Implements heartbeat-based monitoring to track service availability and connection health between distributed nodes.
- Network Connectivity Monitoring - Tracks the real-time online status of remote service providers using periodic heartbeat signals.
- Service Availability Checkers - Uses heartbeat detection to monitor the availability and operational status of remote service providers.
- Provider Version Matching - Groups services and tracks version numbers to ensure clients connect to the correct iteration of a provider.
