Please enable JavaScript.

Coggle requires JavaScript to display documents.

Hexagonal architecture in java - Coggle Diagram

- - - - Can be:
        
        A console or the command line
        
        HTTP API layer and a set of controllers that handle the requests
        
        A cron job
      - Here are the actors who invoke a business process
    - - This part forms the core of the application
      - It serves the requests from the user interface
      - Main components
        
        Entities - the domain objects
        
        Repositories - a list of methods that communicates with the server-side and return a single entity or list of entities
        
        Interactors - domain-specific service classes that implement business logic, validation, etc.
    - - Consists of services that support the business logic
      - Each of them serves a specific purpose and provides resources/data to the business logic layer
      - Can be:
        
        Data sources
        
        Another service or microservice
    - - User-side -> Business Logic: via Interactor
        
        The user-side drives business logic through an interface defined in the business logic - and implemented there
        
        In hexagonal architecture, we call the interfaces ports.
        
        These actors have to adapt their data format and logic to invoke methods from the ports or interfaces, that's why they are also called adapters in hexagonal architecture
      - Business Logic -> Server-side: via Repository
        
        Repositories are nothing but interfaces - defined in the business logic and implemented in the server-side
- - - - Book Entity
      - IBookService
        
        BookService implements IBookService
      - BookRepository
    - - BookConsoleUI
    - - FileDataSource implements BookRepository