How snehalshinde11/banking-app-docker-compose works
This repository provides three small banking HTTP services: account lookup, transaction listing, and notification retrieval/creation. The sampled implementations keep their data in process memory; no service-to-service calls or end-to-end banking workflow are evidenced, so the services are shown as independent APIs. The README describes Docker Compose, Swarm, and image versions, but does not establish runtime request routing. The transaction controller is the only distinct internal layer shown; other implementation details are grouped at their service entry point.
Main entry points: TransactionController.java Transaction controller · server.js Account service · app.py Notification service · TransactionApplication.java Transaction application
Components 6
Account API
- Account service
account-service/server.js
Transaction API
- Transaction application
transaction-service/src/main/java/com/banking/transaction/TransactionApplication.java - Transaction controller
transaction-service/src/main/java/com/banking/transaction/TransactionController.java
Notification API
- Notification service
notification-service/app.py
Other components
- API client
- Health monitor
Connections 10
- API client → Account service: requests accounts
- Account service → API client: returns accounts
- API client → Transaction controller: requests transactions
- Transaction controller → API client: returns transactions
- API client → Notification service: requests notifications
- Notification service → API client: returns notifications
- Health monitor → Account service: checks health
- Health monitor → Transaction controller: checks health
- Health monitor → Notification service: checks health
- Transaction application → Transaction controller: hosts routes