Nepxion/Discovery
Discovery
Discovery is a traffic orchestration library for Spring Cloud microservices that manages blue-green and canary releases through metadata-based routing, circuit breaking, and environment isolation. It provides a centralized framework for distributing routing rules and governance policies dynamically via a remote configuration center, enabling runtime updates without service restarts.
The project distinguishes itself through multi-dimensional traffic control, routing requests based on metadata tags attached to service instances for fine-grained traffic management without code changes. It supports environment and group isolation to enforce deployment boundaries, multi-dimensional failover strategies across environments, regions, zones, versions, or IPs, and plugin-based circuit breaker integration that activates based on service metadata conditions. Traffic dyeing and trace injection capabilities inject release and circuit-breaking metadata into distributed traces for correlation with observability systems.
Additional capabilities include dynamic gateway route management through an API, database and message queue traffic routing for blue-green deployments, graceful service shutdown to prevent traffic loss, and release strategy modeling for automated testing. The library also provides instance blacklisting, service registration limits, and rate limiting based on metadata, along with distributed tracing integration with Jaeger, SkyWalking, or Zipkin and metrics exposure for Prometheus and Spring Boot Admin.
Documentation covers installation, configuration, and usage patterns for integrating the library into Spring Cloud applications.
Features
- Spring Cloud Microservice Orchestrations - A library for managing blue-green and canary releases, routing, circuit breaking, and traffic isolation in Spring Cloud microservices.
- Spring Cloud Canary Controllers - Routes a percentage of traffic to new service versions for gradual rollout testing in Spring Cloud applications.
- Traffic Tagging - Tags service instances with metadata for traffic routing and release management.
- Zero-Downtime Deployments - Switches traffic between two identical environments to enable zero-downtime releases and quick rollbacks.
- Spring Cloud Traffic Routing - Routes requests between microservice instances based on version, region, header, or metadata tags.
- Metadata-Driven Routing - Routes requests based on metadata tags attached to service instances for fine-grained traffic control.
- Metadata-Based - Routes requests between service instances based on version, region, header, or metadata tags for fine-grained traffic control.
- Canary Allocation Routing - Distributes a percentage of traffic to a canary version and the rest to the stable version.
- Weighted Traffic Splitting - Distributes incoming requests across multiple service versions according to configurable weight percentages.
- Environment Isolation - Restricts service calls to instances within the same environment or logical group to enforce deployment boundaries.
- Rule Distribution Endpoints - Distributes routing and governance rules dynamically through a remote configuration center for runtime updates.
- Entity Routing Versioning - Controls which version of a microservice receives a request based on configurable rules and metadata.
- Instance Metadata Tagging - Tags instances with metadata from Git, startup parameters, or configuration files for routing decisions.
- Rate Limiting and Circuit Breaking - Applies rate limiting and circuit breaking based on service metadata like group, version, or region.
- Database and Queue - Routes database and message queue traffic to different instances for blue-green releases.
- Graceful Shutdowns - Removes a service instance from the load balancer before stopping it to ensure no traffic loss.
- Availability Zone Awareness - Redirects requests to a service in another availability zone when the preferred zone is unavailable.
- Metadata-Based - Applies rate limits and circuit breakers based on service metadata such as group, version, or region.
- Regional Routing - Routes requests to services in a specific region for multi-datacenter or multi-active deployments.
- Regional Failover - Redirects requests to a service in another region when the preferred region is unavailable.
- Service Instance Failover - Redirects requests to alternative instances or environments when the preferred target is unavailable.
- Version-Based Failovers - Redirects requests to another service version when the preferred version is unavailable.
- Header-Based Routing - Directs requests to different service versions based on HTTP header values for granular traffic control.
- Conditional Routing - Drives traffic routing decisions using headers, parameters, cookies, or domain names.
- Dynamic Route Management - Provides an API for live gateway route reconfiguration without restarting services.
- Zone-Aware Routing - Routes requests to services in the same availability zone to reduce latency and improve resilience.
- Zone-Based Traffic Isolations - Restricts service calls to instances in the same availability zone for affinity-based routing.
- Service Environment Isolators - Restricts service calls to instances in the same environment, group, or zone for affinity-based routing.
- Group-Based Service Isolations - Restricts service calls to instances within the same logical group to enforce environment isolation.
- Service Environment Isolations - Restricts service calls to instances in the same environment, such as testing or production.
- Metadata-Based - Applies rate limiting and circuit breaking based on service group, version, region, or other metadata tags.
- Plugin-Based - Integrates circuit breaker and rate limiting logic as pluggable modules activated by service metadata.
- Multi-Dimensional - Implements configurable failover across multiple dimensions like environment, region, zone, version, and IP.
- Remote Routing Rule Subscriptions - Subscribes to and applies routing rules from a remote configuration center in real time.
- SpEL Expression Parsers - Uses Spring Expression Language to define dynamic conditions for traffic routing.
- Distributed Tracing - Injects release and circuit-breaker metadata into traces for monitoring with Jaeger, SkyWalking, or Zipkin.
- Traffic Dyeing and Trace Injection - Injects release and circuit-breaking metadata into distributed traces for observability correlation.
- Dynamic Routing - Adds, modifies, deletes, and queries gateway routes at runtime without restarting the server.
- Spring Cloud Gateway Route Managers - Adds, modifies, and queries dynamic routes in the gateway without restarting the service for Spring Cloud.
- Service Environment Failovers - Redirects requests to a service in another environment when the preferred environment is unavailable.
