-
Notifications
You must be signed in to change notification settings - Fork 0
Use case
Kamil Adam edited this page Jun 10, 2026
·
2 revisions
- frontend -> auth service -> keycloak -> bus -> user service
- upgrade user
- Add registration flow: Client -> frontend-react-vite -> http -> bff-nest -> http -> mono/api-gateway -> http -> mono/modulith -> gRPC -> UserService -> Postgre -> Outbox -> bus (RabbitMQ or Kafka) -> module/auth-service -> Spring Cloud Function -> Keycloak
- Add Login flow: Client -> frontend-react-vite -> http -> bff-nest -> http -> module/auth-service -> Keycloak -> JWT
- Add Logout flow: Client -> frontend-react-vite -> http -> bff-nest -> http -> module/auth-service -> Keycloak logout + blacklist (with Redis)
- Add registration flow: Client -> frontend-angular -> http -> BFF -> http -> mono/api-gateway -> http -> mono/modulith -> gRPC -> UserService -> Postgre -> Outbox -> bus (RabbitMQ or Kafka) -> module/auth-service -> Spring Cloud Function -> Keycloak
- Add Login flow: Client -> frontend-angular -> http -> bff-nest -> http -> module/auth-service -> Keycloak -> JWT
- Add Logout flow: Client -> frontend-angular -> http -> bff-nest -> http -> module/auth-service -> Keycloak logout + blacklist (with Redis)
- When user is created, notification service send e-mail
- Registration
- Login, Logout
- Next Bid
- Rest Bidding
- Registration
- Login
- Logout
- Next bid
- Rest Bidding
- Add healthcheck for all microservices
- Integration tests for backend with test containres
- Clean up documentation
- All Kotlin microservices shoud use Config Server
- All Kotlin microservices shoud use Eureca Server
- Different config for server config locally and in dockers
- Rewrite micro to Quarcus and Scala