How jay-abre/payment-gateway-system-springboot works
Project type and purpose
• This is a backend-only, full-blown microservices system (“Digital Wallet Microservice Application”) built on Java/Spring Boot.
• Each service is independently deployed (Docker + docker-compose), communicates via Kafka, and persists to its own PostgreSQL database.
• A shared “common” library holds cross-cutting event definitions and configuration.
File-structure analysis
• Top-level:
– docker-compose.yml (orchestrates services, Kafka, Postgres, Prometheus, Grafana)
– payment-gateway-services/ (root for all microservices + common module + per-service folders)
• Per service (user-service, account-service, transaction-service, payment-gateway-service, bank-reconciliation-service, notification-service):
– src/main/java: standard Spring Boot layers (config, controller, service, repository, security, entity, dto, mapper, exception)
– src/main/resources/application.yml: service-specific configuration (port, DB, Kafka topics, Swagger)
– Dockerfile + mvnw wrapper + pom.xml
– src/test/java: unit/integration tests (TDD style)
• common/: reusable configs and event classes (AccountCreatedEvent, PaymentSuccessEvent, etc.)
README insights
• Microservices with real-time streaming (Kafka).
• Containerized (Docker), monitored (Prometheus/Grafana), logged (SLF4J).
• CI/CD in GitHub Actions.
• Exposed Swagger UIs on distinct ports per service.