Please enable JavaScript.

Coggle requires JavaScript to display documents.

Clean architecture, Ports, https://github.com/alireza-bonab/clean-todo -…

- - - - All entities like the Todo entity goes under entities.
      - if you have entities that carrying logic they should be classes.
      - if some properties so I keep it as an interface
    - - based on user-story definition
      - We identify use-cases based on user stories and the events in the software application
      - Each use-case needs some classes like error classes, RequestDTO and ResponseDTO, and use-case class itself.
        
        Every use-case class extends from a base use-case interface which has an abstract method (execute).
        
        The execute logic is the application-specific business logic and returns the proper ResponseDTO.
        
        It’s an async function so it always returns aPromise<ResponseDTO>.
      - USE CASE - DEFINITIONS - CLASES DE EQUIVALENCIA?
    - - every base-class goes under the definition.
      - UseCase or base UseCaseError
- - - - the data flow which starts from the controller goes through use-case and then goes to the presenter.
        
        ^^^^^^^^
      - The loosely coupled communication is done by the help of Interface Adapters.
        
        This layer exposes a set of interfaces that enables Drivers and Frameworks to attach themselves to the use-cases. In the diagram above you can see that drivers or entry points like web, use interfaces to wrap themselves around ports and then drive actions.
      - On the other hand, I/O components implement ports and let the use-case to accept them as dependency injection and consume the service they expose.
    - - ENTITIES
        
        Object which wraps some business rules as methods over critical business data or properties
        
        EG.
        
        post in a platform
        
        customer in e-commerce
      - USE CASES
        
        application-specific business rule that appears as action with the proper input and internally works with entities to deliver the response.
        
        EG.
        
        checkout
        
        calculate salary
      - GATEWAYS-CONTROLLERS-PRESENTERS or Interface Adapters Layer
        
        Includes interfaces and abstract classes that help the outer layers to communicate with use cases
        
        It holds a set of contracts or adapters for entry points such as WEB or DB to plug them into the business logic
      - WEB-UI-DATABASE
        
        All detail components such as Web Server or Database or any I/O service or any driver goes here.
        
        All of them going to work with Use Cases or application business rules based on contracts in Interface Adapters