Understanding Service Gateways: Concepts, Benefits, and Technical Stack Selection

1. What Is a Service Gateway

Service Gateway = Routing + Filters

1. Routing : receives all external requests and forwards them to backend microservices.

2. Filters : implement cross‑cutting concerns such as authentication, rate limiting, monitoring, etc.; even routing itself is realized through a filter.

2. Why a Service Gateway Is Needed

Cross‑cutting functions (e.g., authentication) can be placed in three locations:

Implemented separately in each service (high redundancy, rarely used).

Encapsulated in a shared common service that every microservice depends on.

Implemented as a pre‑filter in the service gateway, handling every incoming request.

The first approach is clearly undesirable. The second reduces code duplication but introduces two problems: it inflates each service's JAR size (especially problematic for Docker images) and makes upgrades difficult because every service must be re‑compiled when the shared component changes.

The service gateway solves these issues by moving authentication logic into a gateway filter, keeping backend services free of authentication code, reducing JAR size, and allowing authentication changes by updating only the gateway.

3. Service Gateway Technical Selection

The architecture after introducing a gateway consists of three parts: the gateway itself, an open‑service , and the actual services.

3.1 Overall Flow

Gateway, open‑service, and services register themselves with a service registry at startup.

Clients send requests to the gateway, which performs intelligent routing (service discovery, load balancing) and applies authentication, monitoring, and rate limiting before forwarding to the open‑service.

The open‑service aggregates responses from internal services and returns them to the gateway, which then forwards them to the client.

3.2 Considerations When Adding a Gateway

Introducing a gateway adds an extra hop, slightly reducing performance, but the impact is usually small because gateway machines are provisioned with high performance and internal network latency is low.

Single‑point‑of‑failure risk: the gateway, Nginx, DNS, etc., can become a bottleneck. Mitigation strategies include placing a high‑performance Nginx in front of the gateway or deploying multiple gateway instances on powerful hardware after load testing.

The gateway should remain lightweight.

3.3 Basic Functions of a Service Gateway

Intelligent Routing : forwards external requests to the open‑service; internal service‑to‑service calls bypass the gateway.

Authentication : validates user requests to the open‑service; internal calls are not authenticated by the gateway.

API Monitoring : monitors traffic that passes through the gateway and its own performance metrics (e.g., GC).

Rate Limiting : works together with monitoring to limit request rates.

Unified API Logging : records entry and exit logs for each API call, similar to an aspect‑oriented logging mechanism.

Additional capabilities can include A/B testing, experiment configuration, data tracking, and split‑traffic engines, though the split‑traffic logic is often better placed in the open‑service rather than the gateway.

3.4 Technology Stack

Programming language: Java + Groovy (Groovy enables dynamic filter addition without restarting the gateway).

Microservice framework: Spring Boot .

Gateway component: Netflix Zuul (open‑source gateway from Netflix).

Service registry: Consul .

Authentication: JWT .

API monitoring: Prometheus + Grafana .

Unified logging: Logback + ELK stack .

Load testing: JMeter .

The article concludes with a promotional note encouraging readers to share the article and offering paid JetBrains “family‑bucket” licenses, which is unrelated to the technical content.