3. Layered Architecture

In this section, we introduce the Layered Architecture of the AppCraft framework. The architecture follows a clean and modular design, ensuring flexibility and scalability. The system is divided into multiple layers, each with distinct responsibilities, allowing for easy maintainability and extensibility.

The architecture layers are:

1. Runner: The entry points of the application. It initiates the process and calls the Presentation layer or Service layer.

2. Presentation: This layer handles the user interface and presentation logic. It interacts with the Application layer to present data to the user.

3. Application: Manages interactions between the Presentation layer and the Domain layer. It handles business logic and operations, such as calling models from the Domain and managing adapters and frameworks from the Infrastructure.

4. Domain: Represents the core business entities. This layer contains the application’s data models and business rules.

5. Infrastructure: Includes all the external systems, frameworks, and adapters, such as databases, third-party services, file management, and more.

Architecture Layers

• 3.1. Runner Layer
  • 3.1.1. What to Do in Runners
  • 3.1.2. What to Avoid in Runners
  • 3.1.3. Types of runners
  • 3.1.4. Example of a Runner
  • 3.1.5. Running Applications
  • 3.1.6. Running Auxiliary Runner
  • 3.1.7. Executing a Specific Runner
• 3.2. Presentation Layer
  • 3.2.1. What to Do in Presentation
  • 3.2.2. What to Avoid in Presentation
  • 3.2.3. Example of a CLI Presentation
• 3.3. Application Layer
  • 3.3.1. What to Do in Application
  • 3.3.2. What to Avoid in Application
  • 3.3.3. Example of a DTO
  • 3.3.4. Example of a Mapper
  • 3.3.5. Example of a Service
• 3.4. Domain Layer
  • 3.4.1. What to Do in Domain
  • 3.4.2. What to Avoid in Domain
  • 3.4.3. Example of a Model
  • 3.4.4. Example of Repository Interface
  • 3.4.5. Example of Adapter Interface
• 3.5. Infrastructure Layer
  • 3.5.1. Under construction

Application flow

• 3.6. Application Flow
  • 3.6.1. Request Flow
  • 3.6.2. Response Flow