generated from amazon-archives/__template_MIT-0
-
Notifications
You must be signed in to change notification settings - Fork 30
Open
Description
Hi and thanks a lot for this repository.
I am just getting started with the hexagonal architecture (and Rust in general) and I am wondering about some things in the current setup of the hexagonal architecture in this repo:
- Why is
model.rsnot part of the domain? - Why does
lib.rshave the commentDomain logic for the servicebut is not part of the domain? - Why aren't the port traits part of the Domain but part of the
store? And what is a store in the naming conventions of a hexagonal architecture?
Don't get me wrong: I really like the repository, but I wonder if the boundaries could be a little bit more enforced.
When looking at another great example of a hexagonal architecture (in rust) and the source code of it, it looks like it is structured a little bit better, even if there are also issues around some implementation details: alexislozano/pokedex#1
Would it be of interest for you to restructure the existing code? Maybe I can help.
Metadata
Metadata
Assignees
Labels
No labels
