Enterprise Services API
Enterprise backend — 20+ REST endpoints behind Keycloak SSO and HashiCorp Vault, with RBAC, Docker deployment and full Swagger docs.
- Role
- Backend Engineer
- Timeline
- Solo build · 2025
- Year
- 2025
- Status
- Case Study
Microservices · Security
Enterprise Services API
01 The Problem
A growing service surface needed centralised identity, zero hardcoded secrets and predictable deployments — without each service reinventing auth, configuration and documentation.
02 The Solution
A microservices platform where Keycloak owns identity and SSO, Vault owns secrets, and every service ships containerised with generated OpenAPI docs. RBAC is enforced uniformly and the whole stack stands up with a single compose command.
03 What it does
- 20+ documented REST endpoints
- Keycloak single sign-on
- HashiCorp Vault for secrets
- Uniform RBAC across services
- Dockerised, one-command deploy
- Swagger / OpenAPI documentation
04 Architecture
Identity
Keycloak issues tokens & provides SSO across services
Secrets
HashiCorp Vault — no credentials in code or env files
Services
20+ REST endpoints, microservice boundaries
Containerisation
Docker images + compose orchestration
Documentation
Auto-generated Swagger / OpenAPI specs
Data
PostgreSQL with per-service schemas
05 Results
20+
REST endpoints
SSO
Across all services
0
Hardcoded secrets
1-cmd
Deployment