Skip to content

Latest commit

 

History

History
43 lines (30 loc) · 2.26 KB

README.md

File metadata and controls

43 lines (30 loc) · 2.26 KB

Infrastructure Layer

This folder contains the components of the Infrastructure Layer of the project. The Infrastructure Layer is responsible for providing concrete implementations of various services, such as data persistence, message queues, and external APIs.

Structure

The Infrastructure Layer is organized into the following sub-folders:

  • adapters: Contains adapter classes used to convert between different data formats or interfaces.
  • config: Contains configuration files for various infrastructure components.
  • entities: Contains entity classes used for data persistence.
  • handlers: Contains handler classes for various event-driven functionalities, such as API Gateway events, Cognito triggers, and DynamoDB streams.
  • helpers: Contains helper classes and functions used in the infrastructure layer.
  • mappers: Contains mapper classes for converting between domain entities and infrastructure entities.
  • providers: Contains classes responsible for providing instances of infrastructure services.
  • repositories: Contains concrete implementations of repository interfaces for data persistence.
  • services: Contains concrete implementations of domain services, such as authentication and user management.

Usage

The components in the Infrastructure Layer are responsible for:

  1. Implementing concrete services used by the Application and Domain Layers.
  2. Managing data persistence through repositories.
  3. Handling external system interactions, such as messaging and API calls.

Best Practices

When working with the Infrastructure Layer, follow these best practices:

  1. Keep the Infrastructure Layer decoupled from the Application and Domain Layers.
  2. Use adapters and mappers to convert between different data formats or interfaces.
  3. Ensure that infrastructure concerns, such as data persistence and external system interactions, are separated from business logic.
  4. Follow the Dependency Inversion Principle to enable easier testing and maintainability.

Contributing

When adding new functionality to the Infrastructure Layer, ensure that you:

  1. Follow the existing project structure and organization.
  2. Update this README.md file if needed.
  3. Write tests for new components and functionality.
  4. Adhere to the project's coding style and best practices.