> A hexagon defines some ports (the component it needs to work), some adapters
> (the implementations it provides to other hexagons) and a core domain: the
> logic of this hexagon.
Thank you for elaborating your thoughts. I see much better now what you are
trying to do. I like many of the
I realize while looking for resources about hexagonal architecture that
I probably used port/adaptor words differently from what they are
supposed to mean.
I'll ask some friends to correct me on that matter.
On Tue, 2020-05-19 at 20:41 +0900, David Leangen wrote:
> Hi Matthieu,
>
>
[...]
>
>
Hi Matthieu,
>> I would wager that in most situations, this is the level of abstraction that
>> is most useful for a developer or system operator (and definitely for an
>> application assembler). The only time a package or class level is necessary
>> is when actually making changes to the
Hi David,
On Sun, 2020-05-17 at 15:01 +0900, David Leangen wrote:
> Hi!
>
>
[...]
> Organizing into Guice Modules is very nice. One of the important
> benefits is that it helps a lot to break the system down into
> reasonable chunks that are more understandable. It is simply
> impossible for a
On 18/05/2020 16:16, David Leangen wrote:
>
> Thank you for the explanations. I now understand much better the migration
> from Spring to Guice, and the intent behind Guice.
>
> Instead of directly answering the questions you posed, I will make a proposal
> that I think goes in the same
Thank you for the explanations. I now understand much better the migration from
Spring to Guice, and the intent behind Guice.
Instead of directly answering the questions you posed, I will make a proposal
that I think goes in the same direction as your comments.
> This documentation effort
Hi David!
A pretty long and interesting email!
On 17/05/2020 13:01, David Leangen wrote:
>
> Hi!
>
> As I just mentioned in a different email:
>
>> As part of my documentation project, I am starting to turn my attention
>> towards the code itself. I am trying to understand how the system
Hi!
As I just mentioned in a different email:
> As part of my documentation project, I am starting to turn my attention
> towards the code itself. I am trying to understand how the system works. […]
> To understand the system better, I need to take a step back and understand
> Guice. I am
