Skip to content

[Question] Cleanup of hexagonal structure #39

@hffmnn

Description

@hffmnn

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.rs not part of the domain?
  • Why does lib.rs have the comment Domain logic for the service but 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

Screenshot 2022-02-03 at 16 35 22

Would it be of interest for you to restructure the existing code? Maybe I can help.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions