https://angular.love/ports-and-adapters-vs-hexagonal-architecture-is-it-the-same-pattern?utm_campaign=artylul-ports-and-adapters-vs-hexagonal&utm_medium=newsfeed&utm_source=twitter&utm_term=en

[giscus[bot]]

https://angular.love/ports-and-adapters-vs-hexagonal-architecture-is-it-the-same-pattern?utm_campaign=artylul-ports-and-adapters-vs-hexagonal&utm_medium=newsfeed&utm_source=twitter&utm_term=en

Angular.love - a place for all Angular enthusiasts created to inspire and educate.

https://angular.love/ports-and-adapters-vs-hexagonal-architecture-is-it-the-same-pattern?utm_campaign=artylul-ports-and-adapters-vs-hexagonal&utm_medium=newsfeed&utm_source=twitter&utm_term=en

[araujomartin]

Nice post! However, I don't see the adapter pattern being implemented correctly in the service. When you "adapt," you're transforming external resources, such as an API response, into the internal domain of the application.
To make the example clearer, I would add a data mapping step inside FruitServiceAdapter.
Thanks for the community contribution!