How hendi-arch/bank-transfer-app works
Main Components
a) Client Layer
• External clients (Web/Mobile)
• API Gateway (Port 3333)
b) Application Layers (Following Clean Architecture)
1. Infrastructure Layer
• Controllers (REST endpoints)
• Security Components
• Database Repositories
• Schema Definitions
2. Use Case Layer
• Business Logic Components
• Service Implementations
3. Entity Layer
• Domain Models
• Gateway Interfaces
c) Database Layer
• PostgreSQL Database
Component Relationships
• Client requests flow through Security Filters
• Controllers depend on Use Cases
• Use Cases depend on Entity Gateways
• Infrastructure implements Gateway interfaces
• Database Gateways implement Entity Gateway interfaces
Detailed Component Breakdown
Core Modules:
Users Module:
• Authentication/Authorization
• User Management
• Role Management
• Token Management
Transactions Module:
• Fund Transfers
• Transaction Management
Security Layer Representation
A dedicated security section showing:
• JWT Authentication flow
• RBAC Authorization
• Security Filters
• Token Management
Specific Implementation Details
• Clean Architecture boundaries
• Dependency flow (outside-in)
• Interface segregation
• Database access through repositories
• DTO transformations between layers
Key Components to Detail
Controllers:
• UserController
• TransactionController
• UserRoleController
• UserTokenController
Use Cases:
• User Management
• Transaction Processing
• Role Management
• Token Handling
Entities:
• User
• Transaction
• UserRole
• UserToken
Infrastructure:
• Security Filters
• Database Gateways
• Web Configurations