How muratcelikk/bankapp works
This is a small Spring Boot banking API. A client submits a transfer request to the REST controller; the transfer service loads both accounts, checks funds, adjusts balances, and saves them through the JPA repository. The README also advertises an account-listing GET endpoint, though its implementation was not shown. The README names PostgreSQL; the repository-to-database link is therefore shown as unverified. The graph covers the sampled runtime files without inferring unsampled calls.
Main entry points: TransferService.java Transfer Service · AccountRepository.java Account Repository · BankController.java Bank Controller · Account.java Account Entity
Components 7
API
- Bank Controller
src/main/java/com/muratcelik/bankapp/controller/BankController.java - Spring Boot App
src/main/java/com/muratcelik/bankapp/BankAppApplication.java
Transfer Domain
- Transfer Service
src/main/java/com/muratcelik/bankapp/service/TransferService.java - Account Entity
src/main/java/com/muratcelik/bankapp/model/Account.java
Persistence
- Account Repository
src/main/java/com/muratcelik/bankapp/repository/AccountRepository.java - PostgreSQL
Other components
- API Client
Connections 6
- API Client → Bank Controller: requests transfer or lists accounts
README.md - Bank Controller → Transfer Service: dispatches transfer
src/main/java/com/muratcelik/bankapp/controller/BankController.java - Transfer Service → Account Repository: loads and saves
src/main/java/com/muratcelik/bankapp/service/TransferService.java - Transfer Service → Account Entity: checks and updates
src/main/java/com/muratcelik/bankapp/service/TransferService.java - Account Repository → Account Entity: persists entity
src/main/java/com/muratcelik/bankapp/repository/AccountRepository.java - Account Repository → PostgreSQL: persists through JPA