Easegress

Easegress is a cloud-native traffic orchestration platform that functions as a multi-protocol API gateway and service mesh proxy. It routes, transforms, and orchestrates HTTP and MQTT traffic through configurable filter chains, providing high availability, security controls, and resilience for backend services. The platform integrates with service discovery systems like Kubernetes, Consul, and Eureka to dynamically route traffic to discovered services with automatic failover and health monitoring.

The system distinguishes itself through a pipeline-based filter chain architecture where requests pass through a configurable sequence of processing, routing, and transformation steps. It supports canary and blue-green deployment strategies for safe traffic shifting between service versions, and implements circuit breaker, rate limiting, retry, and timeout mechanisms to protect backend services from cascading failures. Security is enforced through JWT, OAuth2, HMAC signature, and IP filter authentication at the pipeline level, while WebAssembly-based custom filter extensions allow users to run their own code for custom request processing and transformation.

The platform provides traffic observability through metrics collection and visualization of latency, throughput, error rates, and status codes for all traffic flowing through the system. It supports hot-update configuration and binary deployment without dropping active connections, and can proxy requests to AI model providers while adapting between different API formats and optionally caching responses in a vector database.

Features

Traffic Orchestration - Routes and manages HTTP, MQTT, and other protocol traffic with high availability, security, and observability in cloud environments.

Multi-Protocol Gateways - Routes and manages HTTP and MQTT traffic through configurable filter chains for authentication, rate limiting, and protocol adaptation.

Traffic Resilience Policies - Applies circuit breakers, rate limiters, retries, and timeouts to protect backend services from failures and overload.

Canary Deployment Controllers - Shifts traffic gradually or instantly between service versions using weighted routing and deployment strategies.

High-Availability Instance Redundancy - Distributes traffic across redundant instances and switches to healthy ones automatically when failures occur.

Health-Based Traffic Rerouting - Monitors backend health and reroutes traffic away from failed instances to maintain continuous service.

Gateway Rate Limiters - Applies configurable rate limiters, retries, and timeouts to prevent cascading failures and control traffic flow.

Service Meshes - Integrates with Kubernetes, Consul, and Eureka service discovery to route traffic with automatic failover and health monitoring.

Traffic Management - Controls traffic flow between services using canary deployments, circuit breakers, and load balancing strategies for resilient operations.

Multi-Protocol Traffic Orchestration - Routes and manages HTTP, MQTT, and other protocol traffic with high availability and security controls.

Traffic Processing Pipelines - Passes requests through a configurable sequence of filters for processing, routing, and transformation.

HTTP Traffic Handling - Routes and load-balances HTTP requests across backend services to ensure reliable delivery and high availability.

Load Balancers - Distributes incoming requests across multiple backend servers using round-robin, random, or hash-based strategies.

Service Traffic Routing - Shifts traffic between service versions using canary or blue-green deployment patterns without interrupting live traffic.

Multi-Protocol Routing - Routes and manages traffic across HTTP, MQTT, and other protocols within a single unified system.

Request Distribution Strategies - Splits incoming requests among multiple backend servers using round-robin, IP hash, or other strategies.

Service Discovery Integrations - Connects with registries like Consul, Eureka, and Kubernetes to dynamically route traffic to discovered services.

Traffic Orchestration Platforms - An API gateway and traffic management system that routes, transforms, and orchestrates HTTP and MQTT traffic.

Traffic Protocol Inspection - Directs and manages traffic for HTTP, MQTT, and other protocols within a single system.

Pipeline-Based Filter Chains - Routes HTTP and MQTT traffic through configurable filter chains for orchestration, security, and resilience.

Revision Traffic Splits - Splits traffic between service versions using canary or blue-green release strategies for safe rollouts.

Authentication and Authorization - Validates requests using JWT, OAuth2, HMAC signatures, IP filters, and static HTTPS certificates.

Request Signature Verification - Checks requests using JWT, OAuth2, HMAC signatures, IP filters, and static HTTPS certificates.

Security and Access Control - Checks request identity and permissions using JWT, OAuth2, HMAC signatures, IP filters, and HTTPS certificates.

Traffic Security Policies - Applies security rules such as rate limiting, IP whitelisting, and authentication to protect backend services from abuse.

JWT Authentications - Verifies request identity and permissions using JWT, OAuth2, HMAC signatures, and IP filters at the pipeline level.

Cascading Failure Preventions - Applies circuit breakers, rate limiters, retries, and timeouts to prevent cascading failures across backend services.

Circuit Breakers - Protects backend services by automatically stopping traffic to failing instances and retrying after a cooldown period.

Request-Response Filter Chains - Passes requests through a configurable sequence of filters for processing, routing, and transformation.

Service Overload Protections - Applies circuit breakers, rate limiters, retries, and timeouts to prevent cascading failures and keep backend services running.

HTTP Request Handlers - Sends incoming HTTP requests to the correct backend service based on configurable rules and conditions.

Traffic Control Policies - Applies authentication, rate limiting, and access control policies to secure traffic flow.

Fault-Tolerant - Keeps traffic flowing and orchestration working continuously even when individual components fail.

External System Integrations - Connects with Kubernetes, service registries, serverless platforms, and distributed tracing backends to extend functionality.

Live Configuration Updates - Updates configuration and binary in place without dropping active connections.

Traffic Pipeline Filters - Develops new pipeline filters using WebAssembly or high-level programming languages for custom request processing and transformation.

MQTT Traffic Routing - Directs incoming MQTT messages to appropriate backend services based on configurable rules.

MQTT Message Handlers - Manages MQTT protocol connections and message delivery for IoT and real-time communication workloads.

MQTT Clients - Handles MQTT protocol traffic, enabling publish/subscribe messaging patterns for IoT and real-time applications.

Traffic Pipeline Filters - Runs user-developed WebAssembly code inside the traffic pipeline to perform custom processing and transformation.

Traffic Pipeline Filters - Runs user-developed WebAssembly code as custom filters within the traffic processing pipeline.

API Aggregators - Combines results from multiple APIs or orchestrates sequences of API calls into a single response.

Metric and Performance Monitors - Collects and visualizes latency percentiles, throughput, error rates, and status codes for traffic and nodes.

Request Traffic Monitors - Collects and displays throughput, latency, error rates, and status codes for each node and traffic type.

Client Traffic Metrics - Collects and visualizes latency, throughput, error rates, and status codes for all traffic flowing through the system.

Traffic Monitoring Tools - Collects and exposes metrics, logs, and traces for all traffic flowing through the system.

easegress-ioeasegress

Features

Star history