One entry point for 30+ microservices
A backend-for-frontend layer on Spring Cloud Gateway, with Keycloak authentication handled in one place instead of per client.
- Role
- Software developer at Intellexi, redesigned the client-facing architecture
- Outcome
- Clients talk to one gateway, and authentication lives in one place.
- Stack
- Java
- Spring Cloud Gateway
- Keycloak
- Docker
- OpenShift
Problem
Clients called 30+ backend microservices directly, and Keycloak authentication was duplicated for each client.
Approach
I redesigned the client-facing architecture around a backend-for-frontend (BFF) pattern on Spring Cloud Gateway. The gateway became the single entry point and took over Keycloak authentication.
Result
- One entry point for 30+ backend microservices.
- Keycloak authentication centralised instead of duplicated per client.