How thomasvitale/spring-cloud-gateway-resilience-security-observability works
Project type and purpose
• This is a small microservices demo built with Spring Boot and Spring Cloud Gateway.
• It shows how to use an API Gateway (edge-service) to route client traffic, enforce OAuth2/OIDC security, apply resilience patterns, and export observability data.
File structure
• Top-level:
• compose.yml – Docker/Podman compose setup including Keycloak and observability services.
• platform/keycloak/full-realm-config.json – Keycloak realm configuration.
• edge-service/… – Spring Boot API gateway (Spring Cloud Gateway + WebFlux + Resilience4J + Spring Security).
• book-service/… – Spring Boot “business” microservice (CRUD books).
• Common patterns: both services use Gradle wrappers, application.yml, test folders, and Micrometer/OpenTelemetry integrations.
README for additional insights
• The gateway: entry point on port 9000, handles routing, resilience (circuit breakers, retries, rate-limiters), security via OAuth2/OpenID Connect.
• The book service: on port 9001, protected by gateway authentication.
• Observability: logs, metrics, traces exported via OTLP → Grafana (started automatically with Arconia Dev Services).
• Keycloak for identity server.