Why I am using Hexagonal Architecture in my projects 

Thank you for your feedback, I will make an effort to work more with the volume to make it better next time

mapstruct

Since I am moving away from the traditional restcontrollers, and is heading towards using GraphQL, DTOs are no longer an issue. This means we no longer have to spend time figuring out what this-or-that DTO should look like, and what data the frontend needs. We can instead focus on what data users have authorization to access, and which data we want to expose. :) I showed a quick sample of how to setup graphql in a spring boot project here, if it is of interest ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-cYb33gp0YOE.html

@@IvanSkodje I've never used GraphQL but after this, I think it's time I take a look at it. Thanks so much, learned a lot from this interaction. Let me check your other video and btw you've earned yourself a subscriber.

Happy you liked it, but I have not made the project public. If/when I get back to it I can see if I am able to create a template project similar to this. Is there anything in particular that peeked your interest?

A great question! You're spot on; there are specific reasons we distinguish between the database classes in the Adapters folder and those we’d typically place in the Infrastructure folder.. ! Adapters are all about converting data between different formats. Since we’re using Spring Boot in this project, much of the heavy lifting and details we’d usually find in the Infrastructure folder are hidden within the annotations we use, thus eliminating the need for explicit database code within the infrastructure folder. In this setup, our Adapters are dealing with the business layer logic, while the specifics of database interaction are managed by the annotations we’re using. This way, we maintain clarity and ensure every part of our architecture has its distinct role, while removing the need to write our own infrastructure logic for the database.

You should implement it on Adapter layer. More specifically driving part.

Download and use the "Dracula Theme" plugin: plugins.jetbrains.com/plugin/12275-dracula-theme

@@IvanSkodje awesome, thought you had some custom color schemes going on. think I just need to upgrade my IntelliJ IDEA a bit ^^

Good catch. The naming may not be good enough, but it essentially implements the desired functionality that we expose via the AccountJpaRepositoryAdapter. The Services within the adapter.out.jpa are details we do not care about (in business). How you choose to implement "registerNewAccount(Account account) {}" is up to you, as long as it is coherent with the other methods, such as "findAccountByEmail", and so on (within reason).

I don't get it.. why aren't all these CRUD methods in the same AccountJpaRepo class? Extending crudRepo means you have it all in one place anyways ​@@IvanSkodje