Understanding Service Gateways: Concepts, Benefits, and Technical Selection

Service gateways combine routing and filters to handle external requests, forwarding them to backend microservices while providing cross‑cutting concerns such as authentication, rate limiting, monitoring, and logging.

Three typical placement options for authentication logic are: each service implements it, a shared library is used, or the gateway’s pre‑filter handles it; the gateway approach avoids code duplication, reduces jar size, and simplifies upgrades.

The article outlines the overall architecture (gateway, open‑service, service), the request flow, and key considerations such as added latency, single‑point‑of‑failure mitigation (e.g., fronting the gateway with Nginx), and keeping the gateway lightweight.

Core gateway functions include intelligent routing, permission verification, API monitoring, rate limiting, and unified logging. Additional capabilities such as A/B testing can be built on top.

Technical stack recommendations: Java + Groovy for dynamic filters, Spring Boot, Netflix Zuul as the gateway, Consul for service registration, JWT for authentication, Prometheus + Grafana for monitoring, Logback + ELK for logging, and JMeter for load testing.

服务网关 = 路由转发 + 过滤器