https://github.com/judacarrillo/hexagonal-architecture-typescript

https://github.com/judacarrillo/hexagonal-architecture-typescript

Last synced: about 1 month ago
JSON representation

• Host: GitHub
• URL: https://github.com/judacarrillo/hexagonal-architecture-typescript
• Owner: JudaCarrillo
• License: mit
• Created: 2024-05-17T04:21:16.000Z (8 months ago)
• Default Branch: main
• Last Pushed: 2024-05-18T19:26:59.000Z (8 months ago)
• Last Synced: 2024-05-19T17:28:35.279Z (8 months ago)
• Language: TypeScript
• Size: 73.2 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# hexagonal-architecture-typescript

This repository applying and explain the concepts of hexagonal architecture

The main services are:

- Dashboard API

- DB

- Control Plane

- FrontEnd

The interaction between services born from request of login, this execute a primary action this action interact with Control Plane and DB services through are adapters

Recommendations at the moment to define the work flow of a services:

Identify ...

1. what are the entry triggers?

2. what are the main ports?

I follow the following nomenclature:

If it's a driver:

for - "what needs to be done?" 

Example:

for - authenticating

    - logging

    - register

  

bad practices:

for - authenticating 

for - logging

for - register

In the first example I englobe the methods in a one action (ports).

In the second example I created as many ports as actions.

Important:

Let us remember that the port limits our actions.

Back to the topic..

This port "authenticating" needed a adapter "authenticator", for this I need to create proxies

Design Pattern "Proxy":

url of pattern