How azeezkenny007/corebanking works
Project type and purpose
• CoreBanking API is a RESTful, backend-only banking service (account management, transactions, secure operations).
• Built on .NET 8 using layered (onion) architecture with separate Presentation, Application, Domain (Core), and Infrastructure layers.
Main components
a. Presentation Layer (CoreBanking.API)
• Controllers (AccountController, TransactionController, WeatherForecastController)
• HTTP server (Kestrel) hosted via Docker/.NET host builder
• Configuration (appsettings.json), Swagger middleware
b. Application Layer (CoreBanking.Application)
• Services / Use-cases: business logic orchestration (e.g. AccountService, TransactionService)
c. Domain Layer (CoreBanking.Core)
• Interfaces (IAccountRepository, ITransactionRepository, etc.)
• Models / Entities (AccountModel, TransactionModel, CustomerModel)
d. Infrastructure Layer (CoreBanking.Infrastructure)
• Repository implementations (AccountRepository, TransactionRepository)
• Data access (Entity Framework, SQL Server)
e. External Systems
• SQL Server (LocalDB / Production DB)
• Docker container registry (if deploying containerized)
f. Cross-cutting
• Logging, Security (JWT, HTTPS), DI Container
Relationships and interactions
• HTTP client → API Controllers
• Controllers → Application Services (via DI)
• Services → Domain Interfaces (IAccountRepository)
• Domain Interfaces → Infrastructure Repositories
• Repositories → Database (SQL Server)
• Lifecycle: Request arrives → Controller → Service → Repository → DB → back up the chain
Architectural patterns and design principles
• Onion (Hexagonal) architecture: dependencies point inward toward the Core
• Dependency Injection: layers are loosely coupled via interfaces in Core
• Separation of Concerns: Presentation vs Business Logic vs Data Access
• RESTful API design, Stateless services
Technologies / Frameworks
• ASP.NET Core (Kestrel, Middleware, Controllers)
• Entity Framework Core
• SQL Server / LocalDB
• Docker (Dockerfile in API project)
• Swagger / OpenAPI
• .NET SDK (launchSettings.json for development)
Detail level
• Essential components (Controllers, Services, Repositories, Models).
• Docker boundary around the API to reflect the Dockerfile.