How keerthan-karthikeya-14/digital-bank-system works
This is a digital banking application with web and stateless API access. Its principal workflow is customer registration or authentication, account access, then deposits, withdrawals, transfers, and transaction-history review. The README documents controllers, business logic, JPA domain models, Thymeleaf views, security, and MySQL, but no source excerpts were provided; the graph therefore omits uncertain internal call wiring.
Components 15
Access and security
- REST controllers
- Security configuration
- JWT security
Web experience
- Web controllers
- Thymeleaf views
- UI assets
Banking operations
- Business services
- Users and accounts
- Banking transactions
- Statements and history
Domain and data
- Request and response DTOs
- Banking entities
- MySQL database
Other components
- Customer
- API client
Connections 12
- Customer → Web controllers: uses portal
- Web controllers → Thymeleaf views: renders pages
- Thymeleaf views → Customer: presents interface
- Customer → REST controllers: calls API
- API client → REST controllers: calls API
- REST controllers → JWT security: authenticates requests
- Web controllers → Security configuration: uses form login
- Business services → Users and accounts: handles accounts
- Business services → Banking transactions: handles money movement
- Business services → Statements and history: provides records
- Business services → Banking entities: uses domain models
- REST controllers → Request and response DTOs: exchanges data