awesome-repositories.com
Blog
awesome-repositories.com

Descubre los mejores repositorios open-source con nuestra búsqueda potenciada por IA.

ExplorarBúsquedas curadasAlternativas open-sourceSoftware autohospedableBlogMapa del sitio
ProyectoAcerca deCómo clasificamosPrensaServidor MCP
Aviso legalPrivacidadTérminos
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
sozu-proxy avatar

sozu-proxy/sozu

0
View on GitHub↗
3,687 estrellas·212 forks·Rust·AGPL-3.0·5 vistaswww.sozu.io↗

Sozu

Sozu is a high-performance, memory-safe reverse proxy and load balancer built in Rust. It is designed to manage HTTP, TCP, and UDP traffic through a multi-process architecture that leverages isolated worker processes to ensure fault tolerance and efficient resource utilization across multi-core hardware.

The project distinguishes itself through a focus on continuous availability and dynamic control. It features a unique binary hot-reloading mechanism and a Unix-socket-based control plane, allowing administrators to update proxy configurations, modify listener settings, and even replace the proxy binary without dropping active client connections or interrupting service. This design ensures that the infrastructure remains responsive and secure during updates and runtime adjustments.

Beyond its core routing capabilities, the proxy provides a comprehensive suite of tools for edge security and traffic management. It handles TLS termination, enforces access control policies, and mitigates protocol-based flood attacks, particularly for HTTP/2 traffic. The system also includes extensive observability features, offering real-time performance monitoring, distributed trace propagation, and structured audit logging for all configuration changes and system events.

Features

  • HTTP Reverse Proxies - Provides a high-performance, memory-safe reverse proxy that supports dynamic configuration and zero-downtime upgrades.
  • Zero-Downtime Binaries Upgrades - Supports replacing the running binary with a newer version while maintaining existing connections and state.
  • Infrastructure Shielding - Shields backend services from direct network exposure by acting as a secure gateway and isolating worker processes in sandboxes.
  • Ingress Load Balancers - Distributes incoming requests across multiple backend clusters to optimize resource utilization and ensure high availability.
  • Process Supervision - Ensures continuous service availability by automatically restarting worker processes that fail during operation.
  • Load Balancers - Distributes incoming HTTP, TCP, and UDP traffic across multiple backend clusters to ensure service availability.
  • Session and Traffic Routing - Manages clusters and backend servers through an event loop that accepts configuration updates at runtime without interrupting active connections.
  • TLS Termination - Handles encryption and decryption at the edge to offload cryptographic processing from backend servers.
  • Traffic Proxying - Routes incoming network requests to backend services using support for multiple protocols with encryption termination.
  • Traffic Routing - Routes incoming requests to configured backend clusters using a multi-process architecture that scales across available CPU cores.
  • Socket-Based Binary Hot-Reloading - Replaces the running proxy binary while preserving active network connections via socket handoffs.
  • Constant-Time Authentication - Restricts frontend access using authentication with constant-time password comparison to prevent timing side-channel attacks.
  • Backend Health Trackers - Lists active backends and clusters with performance data and visual alerts for connectivity or threshold violations.
  • Worker Process Isolation - Restricts worker process privileges to shield backend infrastructure and prevent unauthorized access to system resources.
  • Traffic Load Balancers - Routes HTTP, TCP, and UDP traffic across backend clusters with real-time configuration and health monitoring.
  • Zero-Downtime Upgrades - Routes web traffic to backend services while performing configuration and binary upgrades without dropping active connections.
  • IP Header Managers - Strips or injects client IP headers to ensure backend applications receive accurate source information while preventing header spoofing.
  • Distributed Trace Propagation - Passes distributed tracing headers through the network to maintain request continuity across multiple proxy hops.
  • Dynamic Configuration Managers - Enables runtime updates to proxy settings and cluster definitions via a command socket without service restarts.
  • Flood Mitigations - Applies per-listener thresholds for frame types and protocol violations to protect against common denial-of-service attack vectors.
  • Connection Optimizers - Adjusts stream limits and timeout thresholds to improve data throughput and manage resource consumption effectively during active network sessions.
  • HTTP/2 Proxy Development - Handles connections between clients and backends with support for protocol negotiation, stream prioritization, and built-in protection against protocol-based flood attacks.
  • Traffic Analyzers - Reports active stream counts, flow control status, and frame counters to monitor protocol-specific performance and security violations.
  • Version Negotiation - Exchanges supported communication standards during the initial handshake to ensure the most efficient protocol is used.
  • Stream Multiplexing Management - Handles multiple concurrent streams over a single connection with support for flow control, priority scheduling, and built-in flood mitigation.
  • Edge Traffic Management - Terminates TLS connections and enforces access control policies at the network edge to protect backend infrastructure.
  • Proxy Infrastructure Managers - Manages proxy listeners and backend clusters through a live control plane that accepts runtime configuration changes.
  • SNI Binding Validations - Validates that incoming HTTP requests match the hostname covered by the served security certificate to prevent misdirected requests.
  • HTTP/2 - Parses and manages individual request streams within HTTP/2 connections to enforce flow control and protocol-specific security policies.
  • Runtime Control Sockets - Exposes a local command interface via Unix sockets for dynamic configuration updates and administrative tasks.
  • TCP Proxies - Transmits raw byte streams between frontends and backends to support non-HTTP protocols or direct socket-level communication.
  • Traffic Protocol Inspection - Analyzes and manages HTTP/2 streams and protocol-specific traffic to mitigate flood attacks.
  • UDP Proxies - Routes datagram-based traffic like DNS and syslog through load-balanced listeners with active health monitoring.
  • Frontend Authentication - Requires and validates credentials on specific frontends to restrict access to backend services.
  • Administrative Access Restrictions - Validates the identity of connected clients using socket credentials to ensure only authorized users can issue configuration commands.
  • Network Attack Mitigations - Protects against common protocol and network-level attacks by filtering malicious traffic patterns and enforcing rate limits.
  • Proxy Security Header Enforcements - Injects security headers on HTTPS connections to mandate secure browser communication and prevent protocol downgrades.
  • Request Rate Limiting - Protects backend services from overload by enforcing request volume limits on incoming traffic.
  • TLS Certificate Management - Configures default or hostname-based certificates for HTTPS listeners to secure incoming traffic.
  • Non-Blocking Event Loops - Processes network events using a non-blocking loop to handle high concurrency with minimal overhead.
  • Process Isolation Architectures - Distributes incoming traffic across isolated worker processes to leverage multi-core hardware and ensure fault isolation.
  • Shared-Nothing Architectures - Maintains proxy state within individual worker processes to eliminate lock contention and improve performance.
  • Event Auditors - Streams a color-coded log of control-plane events and state changes to identify system transitions or failures as they occur.
  • Runtime Visualizers - Monitors clusters, backends, listeners, and security events in real-time using a live terminal-based interface.
  • Health Checks - Monitors the status of backend services to ensure traffic is only routed to healthy and responsive instances.
  • Metrics Exporters - Exports internal state and performance statistics using standard protocols to external monitoring systems.
  • Real-time Performance Monitoring - Displays real-time metrics for clusters, backends, and listeners through an interactive terminal interface.
  • Security Audit Logs - Logs all configuration mutations and administrative actions to secure files for compliance and security visibility.
  • Control Plane Audit Logs - Logs all privileged configuration mutations and administrative commands to a structured audit sink for security compliance.
  • Telemetry Exporters - Streams telemetry and metrics to external monitoring systems using standard protocols for real-time performance tracking.
  • Parsing Validators - Exercises frame parsing logic against arbitrary inputs to detect memory safety issues and vulnerabilities in header and body processing.
  • Request Context Propagation - Generates or propagates unique request identifiers across proxy hops to enable end-to-end tracing and correlation.

Historial de estrellas

Gráfico del historial de estrellas de sozu-proxy/sozuGráfico del historial de estrellas de sozu-proxy/sozu

Búsqueda con IA

Explora más repositorios increíbles

Describe lo que necesitas en lenguaje sencillo: la IA clasifica miles de proyectos open-source curados por relevancia.

Start searching with AI

Colecciones destacadas con Sozu

Colecciones seleccionadas manualmente donde aparece Sozu.
  • una herramienta para crear túneles inversos seguros
  • Gateways de API y proxies inversos

Preguntas frecuentes

¿Qué hace sozu-proxy/sozu?

Sozu is a high-performance, memory-safe reverse proxy and load balancer built in Rust. It is designed to manage HTTP, TCP, and UDP traffic through a multi-process architecture that leverages isolated worker processes to ensure fault tolerance and efficient resource utilization across multi-core hardware.

¿Cuáles son las características principales de sozu-proxy/sozu?

Las características principales de sozu-proxy/sozu son: HTTP Reverse Proxies, Zero-Downtime Binaries Upgrades, Infrastructure Shielding, Ingress Load Balancers, Process Supervision, Load Balancers, Session and Traffic Routing, TLS Termination.

¿Qué alternativas de código abierto existen para sozu-proxy/sozu?

Las alternativas de código abierto para sozu-proxy/sozu incluyen: linkerd/linkerd2 — This project is a service mesh platform designed to manage, secure, and observe service-to-service communication… cloudflare/pingora — Pingora is a Rust-based framework for building high-performance network services, including HTTP reverse proxies,… mosn/mosn — Mosn is a multi-protocol network proxy designed for cloud-native service meshes, API gateway management, and… optimalbits/redbird — Redbird is a Node.js reverse proxy used to route external network traffic to internal servers. It functions as a layer… nginx/kubernetes-ingress — The NGINX Ingress Controller is a Kubernetes-native traffic manager that handles external requests and routes them to… fosrl/pangolin — Pangolin is a zero-trust remote access platform designed to provide secure, identity-aware connectivity to private…

Alternativas open-source a Sozu

Proyectos open-source similares, clasificados según cuántas características comparten con Sozu.
  • linkerd/linkerd2Avatar de linkerd

    linkerd/linkerd2

    11,424Ver en GitHub↗

    This project is a service mesh platform designed to manage, secure, and observe service-to-service communication within Kubernetes clusters. It functions as a control plane that orchestrates transparent sidecar proxies, which intercept and manage network traffic to provide reliable connectivity for microservices. By automating the injection of these proxies, the platform ensures that infrastructure-level policies are applied consistently across all workloads without requiring manual configuration changes. The platform distinguishes itself through its focus on zero-trust security and cross-clu

    Gocloud-nativegolangkubernetes
    Ver en GitHub↗11,424
  • cloudflare/pingoraAvatar de cloudflare

    cloudflare/pingora

    26,833Ver en GitHub↗

    Pingora is a Rust-based framework for building high-performance network services, including HTTP reverse proxies, layer seven load balancers, and TLS termination proxies. It serves as an asynchronous network library designed to intercept and route HTTP, gRPC, and WebSocket traffic between clients and upstream backend servers. The project enables zero-downtime service updates by handing over listening sockets between processes during binary or configuration upgrades. It utilizes a programmable multi-phase pipeline to modify request and response bodies and headers, and it provides a pluggable T

    Rust
    Ver en GitHub↗26,833
  • mosn/mosnAvatar de mosn

    mosn/mosn

    4,517Ver en GitHub↗

    Mosn is a multi-protocol network proxy designed for cloud-native service meshes, API gateway management, and distributed load balancing. It forwards layer four and layer seven traffic across diverse network protocols to ensure interoperability between distributed cloud components. The project is distinguished by its ability to perform zero-downtime proxy updates, replacing the running binary while maintaining existing network connections. It further supports dynamic proxy extension, allowing custom request processing logic to be added via external plugins or compiled Go modules without restar

    Godata-planeproxyservice-mesh
    Ver en GitHub↗4,517
  • optimalbits/redbirdAvatar de OptimalBits

    OptimalBits/redbird

    4,412Ver en GitHub↗

    Redbird is a Node.js reverse proxy used to route external network traffic to internal servers. It functions as a layer 7 load balancer that maps incoming requests from specific domains or hosts to target upstream servers, shielding backend services from direct public exposure. The project features dynamic route management, allowing routing rules to be updated programmatically at runtime. It synchronizes these routes automatically by polling external sources such as Docker containers and etcd clusters to align proxy configurations with service lifecycles. Additional capabilities include SSL a

    TypeScript
    Ver en GitHub↗4,412
Ver las 30 alternativas a Sozu→