graph LR
Application["Application"]
Core["Core"]
Infrastructure["Infrastructure"]
Web["Web"]
Application -- "depends on" --> Core
Application -- "depends on interfaces from" --> Infrastructure
Web -- "depends on" --> Application
click Application href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/CleanArchitecture/Application.md" "Details"
click Core href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/CleanArchitecture/Core.md" "Details"
click Web href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/CleanArchitecture/Web.md" "Details"
One paragraph explaining the functionality which is represented by this graph. What the main flow is and what is its purpose.
Application [Expand]
The Application Layer (also known as the Use Cases Project) defines application-specific business logic, use cases (commands and queries), Data Transfer Objects (DTOs), and application services. It orchestrates interactions with the Core (Domain) layer and utilizes interfaces (ports) defined in the Core layer, which are then implemented by the Infrastructure layer. It also defines interfaces for Infrastructure services, adhering to the Dependency Inversion Principle.
Related Classes/Methods: None
Core [Expand]
Core component.
Related Classes/Methods: None
Infrastructure component.
Related Classes/Methods: None
Web [Expand]
Web component.
Related Classes/Methods: None