How daohainam/clean-architecture-miniatm works
Project type and purpose
• The project is an example mini-ATM application designed to teach Clean Architecture principles. Notice that it’s used in a video series on Clean Architecture.
• Its core focus is on separating concerns into different layers, such as Domain (Entities), Application (Use Case), and Infrastructure (data persistence, web presentation, external resources).
File structure for layer identification
• Domain/Entities: The MiniATM.Entities folder encapsulates the domain models (e.g., BankAccount, Customer, Transaction) along with domain events and exceptions.
• Application/Use Cases: Under MiniATM.UseCase (and MiniATM.UseCase.Caching), you find business logic components like CashWithdrawalManager and TransferManager, along with interfaces and repository contracts. This represents the “Application” or “Use Case” layer.
• Infrastructure: There are multiple implementations in the MiniATM.Infrastructure layer:
• Data persistence implementations with InMemory and SqlServer projects, including repositories and unit-of-work classes. The SqlServer project includes migration files and database context.
• Web presentation: Controllers (e.g., CoreBankingController, HomeController) and Razor views (under Views) that act as the entry point for user interactions.
• Supporting components such as cash storage and caching.
• Additional supporting folders include DBScripts and Tests, which are used to set up the database and verify functionality respectively.
Relevant technologies, frameworks, and libraries
• .NET/C# (indicated by .csproj files and C# source code).
• Entity Framework for SQL Server migrations and repository mapping (evident from the Migrations folder and MapperProfile).
• ASP.NET MVC (Controllers, Razor Views) for web presentation.
• JavaScript and CSS libraries (Bootstrap, jQuery) found under wwwroot.
Final detailed advice
• Clearly delineate boundaries between layers; this is the key principle of Clean Architecture being demonstrated.
• Verify that all external libraries (like Bootstrap, jQuery) and runtime configuration elements (like appsettings.json, launchSettings.json) are noted as supporting components, providing context to the deployment environment.