Architecture¶

bITdevKit is designed around clean architecture with modular vertical slices. The goal is to keep business logic explicit, testable, and isolated from infrastructure choices.

High-level architecture map¶

flowchart TB
    Presentation[Presentation]
    Infrastructure[Infrastructure]
    Application[Application]
    Domain[Domain]

    Presentation --> Application
    Infrastructure --> Application
    Infrastructure --> Domain
    Application --> Domain

Layer responsibilities¶

Domain¶

aggregates, entities, value objects, typed ids
domain events, domain policies, and business rules
no dependency on outer layers

Application¶

commands, queries, handlers, DTOs, specifications
orchestration through requester/notifier flows
depends on domain, not on infrastructure

Infrastructure¶

persistence, messaging transports, queue brokers, storage providers
implements abstractions required by inner layers
contains integration details and operational mechanics

Presentation¶

minimal API endpoints, web-facing modules, console-facing features
request/response mapping and endpoint composition

Modular vertical slices¶

The preferred shape is a modular monolith where each module owns its own domain, application, infrastructure, and presentation concerns.

Module/
├── Module.Domain
├── Module.Application
├── Module.Infrastructure
└── Module.Presentation

This keeps business capabilities cohesive while still allowing a single host application to compose many modules together.

Request flow in practice¶

sequenceDiagram
    participant Client
    participant Endpoint as Presentation Endpoint
    participant Requester as IRequester
    participant Handler as Application Handler
    participant Domain as Aggregate
    participant Repository as Repository / Provider

    Client->>Endpoint: HTTP request
    Endpoint->>Requester: SendAsync(command/query)
    Requester->>Handler: Dispatch through behaviors
    Handler->>Domain: Execute business logic
    Handler->>Repository: Persist or query
    Repository-->>Handler: Result
    Handler-->>Requester: Result
    Requester-->>Endpoint: Result
    Endpoint-->>Client: HTTP response