Understanding Service Gateways: Concepts, Benefits, and Technical Choices

What is a service gateway

A service gateway combines routing and filtering, acting as a central entry point that receives all external requests and forwards them to backend microservices.

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

Routing forwards requests, while filters implement cross‑cutting concerns such as authentication, rate limiting, and monitoring.

Why a service gateway is needed

Embedding cross‑cutting logic (e.g., permission checks) directly in each service leads to duplicated code, larger JARs, and difficult upgrades. Placing this logic in a gateway filter keeps services lightweight and allows centralized updates without redeploying every microservice.

Technical selection

The proposed architecture consists of three parts: the service gateway, an open‑service layer, and the actual services. All components register with a service registry (Consul) and the gateway performs intelligent routing, load balancing, authentication, monitoring, and rate limiting before forwarding requests to the open‑service.

Key considerations when adding a gateway

Performance impact is modest; the gateway typically runs on powerful hardware and communicates with internal services over fast LAN.

To avoid a single point of failure, place a high‑performance Nginx in front of the gateway or deploy multiple gateway instances.

The gateway should remain lightweight.

Basic gateway functions

Intelligent routing: forwards external requests to open‑service.

Permission validation: checks user requests at the gateway level.

API monitoring: tracks gateway traffic and its own performance metrics.

Rate limiting: works together with monitoring to control traffic.

Unified API logging: records entry and exit logs for each request.

Additional capabilities such as A/B testing can be built on top of the gateway, though some components (e.g., split‑engine) may be better placed in the open‑service.

Proposed technology stack

Programming language: Java + Groovy (allows dynamic filter addition without restarting).

Microservice framework: Spring Boot.

Gateway component: Netflix Zuul.

Service registry: Consul.

Authentication: JWT.

Monitoring: Prometheus + Grafana.

Log aggregation: Logback + ELK stack.

Load testing: JMeter.