Skip to content

on_boarding.md

Latest commit

 

History

History
83 lines (52 loc) · 6.82 KB

on_boarding.md

File metadata and controls

83 lines (52 loc) · 6.82 KB
graph LR
    Web_API["Web API"]
    Application_Layer["Application Layer"]
    Domain_Layer["Domain Layer"]
    Infrastructure_Persistence["Infrastructure - Persistence"]
    Infrastructure_Configuration_Database["Infrastructure - Configuration & Database"]
    Web_API -- "Sends Commands/Queries" --> Application_Layer
    Application_Layer -- "Returns Results" --> Web_API
    Application_Layer -- "Invokes Domain Logic" --> Domain_Layer
    Application_Layer -- "Interacts via Repository Port" --> Domain_Layer
    Infrastructure_Persistence -- "Implements Repository Port" --> Domain_Layer
    Infrastructure_Persistence -- "Maps Entities" --> Domain_Layer
    Infrastructure_Persistence -- "Uses Database Connection" --> Infrastructure_Configuration_Database
    Infrastructure_Configuration_Database -- "Provides Settings" --> Application_Layer
    Infrastructure_Configuration_Database -- "Provides Settings/Connections" --> Infrastructure_Persistence
    click Web_API href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/python-archetype/Web_API.md" "Details"
    click Application_Layer href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/python-archetype/Application_Layer.md" "Details"
    click Domain_Layer href "https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/python-archetype/Domain_Layer.md" "Details"
Loading

CodeBoardingDemoContact

Details

The python-archetype project is structured around a clean architecture, emphasizing separation of concerns and maintainability. The Web API acts as the external entry point, receiving requests and forwarding them as Commands or Queries to the Application Layer. This layer orchestrates the application's core business logic, invoking Domain Logic within the Domain Layer and interacting with Infrastructure - Persistence through Repository Ports defined by the Domain Layer. The Infrastructure - Persistence component provides concrete implementations for these repository ports, handling data storage and retrieval, and mapping Domain Entities to persistence-specific structures. Both the Application Layer and Infrastructure - Persistence rely on Infrastructure - Configuration & Database for essential settings and database connections, ensuring a clear flow of data and dependencies throughout the system.

Web API [Expand]

The external interface for the microservice, responsible for handling incoming HTTP requests, routing them to the appropriate application services, and formatting responses using Data Transfer Objects (DTOs).

Related Classes/Methods:

Application Layer [Expand]

This layer orchestrates the application's business logic. It contains distinct command handlers for write operations and query handlers for read operations, processing Application Commands and Application Queries, and managing Application Query Results. It interacts with the Domain Layer and Infrastructure via ports.

Related Classes/Methods:

Domain Layer [Expand]

The core of the application, encapsulating the essential business rules, Domain Entities, Domain Services, and defining Domain Repository Ports (interfaces). It is independent of external concerns and technology choices.

Related Classes/Methods:

Infrastructure - Persistence

Provides concrete implementations (adapters) for the Domain Repository Ports defined in the Domain Layer. It handles the actual data storage and retrieval mechanisms, mapping between domain entities and database-specific structures (e.g., MongoDB documents).

Related Classes/Methods:

Infrastructure - Configuration & Database

Manages application-wide configuration settings, environment variables, and establishes connections to external resources, primarily the database. It provides these settings and connections to other infrastructure components and the Application Layer.

Related Classes/Methods:

FAQ