manba
HTTP API Gateway
RepoPi no longer tracks this repository daily. Stats below were last updated on 2026-07-25. See current data on GitHub.
💡 Why It Matters
This HTTP API gateway targets teams needing a unified layer to manage backend APIs with features like traffic control, circuit breaking, load balancing, and API aggregation. It separates concerns into two components: a stateless proxy handling client requests and an API server managing metadata via gRPC and REST, supporting service discovery and plugin extensions. The routing system allows traffic diversion and duplication based on HTTP attributes, enabling use cases like A/B testing. Despite a solid feature set, the project shows limited recent activity with its last commit in mid-2023 and moderate popularity at just over 3,000 stars, without notable growth. It suits teams comfortable with Go and Docker who want a configurable gateway with built-in Prometheus metrics and JWT support. Avoid this if you require a more widely adopted or actively maintained gateway such as Kong, Traefik, or Ambassador, especially in environments demanding extensive plugin ecosystems or cloud-native integrations.
🎯 When to Use
Choose this gateway when you need a lightweight, Go-based API gateway that supports advanced routing rules and API aggregation with an integrated management UI. Consider Kong or Traefik instead if you require richer plugin ecosystems, broader community support, or tighter integration with Kubernetes environments.
👥 Team Fit & Use Cases
Typically deployed in microservice architectures requiring centralized API access control, traffic shaping, and backend service health checks. It fits teams building internal API platforms or exposing multiple backend services through a single entry point, often in containerised environments using Docker.
🏷️ Topics & Ecosystem
📊 Activity
Latest commit: 2023-07-12. Activity data is based on daily RepoPi snapshots of the GitHub repository.