rapter1990/insurance-campaign-microservices

Purpose and Runtime Topology

This Maven multi-module system is an insurance campaign-management platform built on Java 25 and Spring Boot 4. It exposes REST APIs for identity, campaign lifecycle, dashboards, and logs; uses independent service data stores; and runs either fully containerized or with infrastructure-only local Compose.

• Root orchestration: pom.xml, docker-compose.yml, docker-compose-local.yml

• Service entry points: api-gateway/src/main/java/com/casestudy/insurancecampaign/gateway/ApiGatewayApplication.java, campaign-service/src/main/java/com/casestudy/insurancecampaign/campaign/CampaignServiceApplication.java

Platform Control Plane and Edge

Discovery Server provides Eureka registration; Config Server centrally serves Spring configuration. API Gateway is the primary client entry point: routes requests to services, validates JWTs, applies Redis-backed rate limits, and aggregates/falls back OpenAPI documents.

• discovery-server/src/main/java/com/casestudy/insurancecampaign/discovery/DiscoveryServerApplication.java

• config-server/src/main/java/com/casestudy/insurancecampaign/config/ConfigServerApplication.java

• api-gateway/src/main/java/com/casestudy/insurancecampaign/gateway/filter/GatewayJwtAuthenticationFilter.java

• api-gateway/src/main/java/com/casestudy/insurancecampaign/gateway/config/GatewayRateLimiterConfiguration.java

Identity and Authorization Boundary

Auth Service owns users, roles, refresh tokens, password-reset tokens, and RSA access-token signing. It persists identity state in its PostgreSQL database through JPA/Liquibase. Other services and the gateway validate signatures with the shared public-key security module; campaign authorization is additionally enforced within Campaign Service, not trusted solely to the gateway.

• auth-service/src/main/java/com/casestudy/insurancecampaign/auth/controller/AuthController.java

• auth-service/src/main/java/com/casestudy/insurancecampaign/auth/service/AuthService.java

• security/src/main/java/com/casestudy/insurancecampaign/security/ServiceSecurityConfiguration.java

• auth-service/src/main/resources/db/changelog/db.changelog-master.yml

Campaign Lifecycle Core

Campaign Service is the system of record for campaigns and status history. Its service layer validates title/category/content rules, rejects duplicate category-title-description combinations, assigns initial status, enforces valid approval/deactivation transitions, persists state/history, and serves REST plus gRPC. It caches campaign status statistics in Redis and evicts cache entries on changes.

• campaign-service/src/main/java/com/casestudy/insurancecampaign/campaign/service/CampaignService.java

• campaign-service/src/main/java/com/casestudy/insurancecampaign/campaign/entity/CampaignEntity.java

• campaign-service/src/main/java/com/casestudy/insurancecampaign/campaign/entity/CampaignStatusHistoryEntity.java

• campaign-service/src/main/java/com/casestudy/insurancecampaign/campaign/grpc/CampaignGrpcEndpoint.java

Dashboard and Interservice Contracts

Dashboard Service is a read-oriented HTTP façade for campaign statistics and campaign history. It does not directly access the campaign database; it calls Campaign Service’s gRPC endpoint using generated protobuf contracts. Auth audit logging instead uses HTTP Exchange from Auth Service to Log Service and is deliberately non-blocking to authentication outcomes through Resilience4j circuit breaker, retry, and bulkhead controls.

• dashboard-service/src/main/java/com/casestudy/insurancecampaign/dashboard/client/CampaignGrpcClient.java

• grpc-contract/src/main/proto/campaign.proto

• auth-service/src/main/java/com/casestudy/insurancecampaign/auth/client/LogServiceHttpClient.java

• auth-service/src/main/java/com/casestudy/insurancecampaign/auth/service/AuthAuditService.java

Eventing and Log Persistence

Campaign changes and slow-request observations are emitted through Kafka; Log Service consumes slow-request events and sends failed processing to a DLQ. Log Service also receives auth audit HTTP calls. Both audit and slow-request records are stored in Elasticsearch, separating searchable operational/business logs from normal application file logs.

• common/src/main/java/com/casestudy/insurancecampaign/common/event/CampaignStatusChangedEvent.java

• common/src/main/java/com/casestudy/insurancecampaign/common/web/SlowRequestLoggingFilter.java

• log-service/src/main/java/com/casestudy/insurancecampaign/log/service/SlowRequestLogConsumer.java

• log-service/src/main/java/com/casestudy/insurancecampaign/log/config/KafkaDlqConfiguration.java

Shared Cross-Cutting and Observability

common standardizes API envelopes, exception mapping, Kafka JSON, virtual-thread setup, HTTP observations, and slow-request publication. Services export actuator metrics to Prometheus and traces through the OpenTelemetry Collector to Tempo; file logs flow via Promtail to Loki. Grafana provisions all three data sources and a campaign dashboard.

• common/src/main/java/com/casestudy/insurancecampaign/common/exception/GlobalExceptionHandler.java

• observability/otel-collector/otel-collector.yml

• observability/prometheus/prometheus.yml

• observability/grafana/dashboards/campaign-logs-traces.json