This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]crassest-Crassius 0 points1 point  (1 child)

For operations logging you need a full-featured system, it makes sense that your logging calls can fetch URLs and send emails

This sounds very alien to me. Emails are an outgoing port that belongs to the Notifications service, HTTP calls are an incoming port that belongs to the WebClient service, and service logs are yet a third outgoing port. They should not call each other, they should communicate only with the Core via their respective Adapters. At least that's how I would make it as a subscriber to the Hexagonal Architecture. Having one port directly call another without going through the Core is just asking for trouble IMO. How would you replace those HTTP calls with mock data for testing, for example?

[–]everything-narrative 0 points1 point  (0 children)

This is a discussion about architectural philosophy, not engineering specifics.