Please enable JavaScript.
Coggle requires JavaScript to display documents.
What is Architecture? ch. 15-16 - Coggle Diagram
What is Architecture?
ch. 15-16
"you don't even have to decide if the system will be delivered over the web"
policy first!
and choosing the details is deferred
feedback also is deferred?
a good architecture should be easily deployable!
slicing into vertical slides allow you to get feedback faster
Chap. 15 - sta suggerendo allora un tipo di sviluppo che parta dal dominio senza passare dai “dettagli”?
it depends by what you want to discover
essence vs learning
Decoupling >>> Duplication
different use cases may change for different reasons and at different rates
are they similar?
extract duplication?
resist the temptation to extract the duplication
add order
delete order
each use case may have "its own" order model?
view order
or should we put the order model in a "shared lib" used by the 3 use cases?
it depends by the team structure
same team handling the 3 use cases?
easier to have a shared lib
resources
sandi metz
https://verraes.net/2014/08/dry-is-about-knowledge/
udi dahn
uncle bob
chapter 16 - the decoupling mode (source level, binary level, execution unit level) is a "detail"?
what if you chose a "big" framework?
e.g. Rails?
share nothing
"Architecture should reveal operation." guardando l'operational part devo riconoscere quale componente si occupa di quale use-case?
operation == use cases? intent of the system
operation = operational needs of the system?
Chap 15: Where are the non-functional requirements or high-level decisions? Should be considered as "details"?
Yes!
Eventual consistency? Microfrontend?
what about the complexity that we got pushing the architecture in this direction
decoupling layers and use cases
partitioning the system in independently changeable componenens
