Initial Discussion: High-level architecture modeling

nahueltaibo / NetCoreRover

MIT License

2 stars 1 forks source link

Initial Discussion: High-level architecture modeling #3

Open nkendoka opened 4 years ago

nkendoka commented 4 years ago

whiteBoardDiagram

TBD:

Identifying App main layers
Layers Responsibilities
Introducing Internal Bus as shared communication channel or some kind of Message transfer mechanism ?

so far:

Domain Layer
Controller Layer
Driver Layer

nahueltaibo commented 4 years ago

Adding The layer diagram available as part of the solution in its current status

turboslon commented 4 years ago

I'm not familiar with the discussion that took place on your previous meeting, but from what I see here, I've got a question: Did you consider Actor concept? For the behavior that should be followed through time and might be affected (paused, cancelled, changed) by external conditions and current state, it's worth considering. Otherwise, behavioral and reactive layers might become a bit tricky to design.

nahueltaibo commented 4 years ago

Sounds interesting! I'm not aware of that, so I'd like to get more information on it. Maybe we can get ideas from there, to make our architecture better.