A cloud-native high-performance proxy for edge, middle, and service communication in microservices architectures.
Envoy is a high-performance, cloud-native proxy designed for edge, middle, and service communication in microservices architectures. It handles critical networking functions like load balancing, observability, and security, providing a universal data plane for modern distributed applications. It solves the problem of managing complex network traffic and ensuring reliability across services.
Platform engineers, SREs, and developers building or managing microservices-based applications who need robust networking, observability, and security features. It's particularly valuable for teams operating in cloud-native environments like Kubernetes.
Developers choose Envoy for its high performance, extensibility, and comprehensive feature set that includes advanced load balancing, dynamic configuration, and detailed observability. Its CNCF backing and active community ensure reliability and continuous innovation for production workloads.
Cloud-native high-performance edge/middle/service proxy
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a consistent API for configuring networking across environments, abstracting complexity as per the philosophy, which is key for microservices.
Supports various algorithms and health checking, crucial for resilient microservices, as highlighted in the key features and blog posts.
Offers detailed metrics, logging, and tracing, enabling deep monitoring of network traffic, which is essential for distributed systems.
Enables runtime updates without restarting using xDS APIs, reducing downtime and allowing seamless changes, as mentioned in the documentation.
Configuration and management require expertise in networking and Envoy's specific APIs, making it challenging for newcomers without prior experience.
The high-performance features come at the cost of higher memory and CPU usage compared to simpler proxies, which may not suit resource-constrained environments.
As per the README, ppc64le builds are best-effort and not covered by the security policy, posing risks for deployments on non-standard architectures.