Lesson189 - Architectural Quantum Tradeoffs

Подписаться 36 тыс.

Просмотров 2,4 тыс.

50% 1

The concept of an architectural quantum was first introduced in the book “Building Evolutionary Architecture”, and further refined in our book “Software Architecture: The Hard Parts”. The architectural quantum concept, which I described in Lesson 138, is a very important aspect to software architecture as it helps us understand the partitioning and dependencies between components, services, and even systems. However, as with all things in software architecture, it comes with a price. In this lesson I firest review the concept of an architectural quantum, then demonstrate some of the tradeoffs associated with this concept.
Architectural Quantum: www.developert...
Head First Software Architecture: amzn.to/3VNFI0o
Software Architecture Monday: bit.ly/3dadEe3
Fundamentals of Software Architecture: amzn.to/3rgFLjY
Software Architecture: The Hard Parts: amzn.to/3BjMMF2

Опубликовано:

27 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 18

@BlindVirtuoso 3 месяца назад

Hi Mark. This one is excellent, I highly appreciate. Coupling and cohesion are the roots of all architectural matters.

@markrichards5014 3 месяца назад

I agree, which is why I am fascinated with this quantum concept.

@BlindVirtuoso 3 месяца назад

@@markrichards5014 Yep, it's really brilliant. Thank you.

@АлександърЦветанов-и1н Месяц назад

Hey Mark, it was a great explanation, I am currently reading the book Fundamentals of Software Architecture and now it totally makes sense because it was but confusing for me. However, may I ask you - in the creation of the ticket trough asynch call to ticket router, even though it is async, if we use synchronous call to a DB or some other component which is shared between two services, than we can consider that they are in one quantum, is that right? If we look for an example, we have 2 services S1 and S2 and they are talking asynchronously between each other but share same DB. In this case they are in one quantum. However if they are using two separate DB, they are in two different quantums?

@markrichards5014 Месяц назад

That is correct! Because they share a DB synchronously, that puts them in the same quantum

@АлександърЦветанов-и1н Месяц назад

@@markrichards5014 Thank you a lot, totally makes sense. A huge thank you for the great book, btw. :)

@HemalVarambhia 2 месяца назад

RSpec has released its equivalent of ArchUnit it "depends" do ... end

@SadSadDeadM 3 месяца назад

User interface for ticket creation could use micro front-end/ module federation approach

@markrichards5014 3 месяца назад

Correct - and that would help separate the quanta.

@MarusykRoman 2 месяца назад

very architectural t-shirt 😁😁

@zxyi9090 3 месяца назад

Isn't operational reporting quanta depends on data aggregation from other services

@zxyi9090 3 месяца назад

Which is async so it makes it separately deployable unit 🎉

@markrichards5014 3 месяца назад

@@zxyi9090 That is correct! If it were synchronous, then yes, it would be a single quantum.

@suchoudh 3 месяца назад

❤first comment ❤

@mahdi5796 3 месяца назад

Thank you. I'm reading your books but still I find your videos very insightful. May I ask, does architectural quantum equate to bounded context in domain-driven design? If not, can you please elaborate why?

@markrichards5014 3 месяца назад

Not directly; the architectural quantum is a physical architecture concept relating the the physical artifacts of the system. A single quantum can contain many bounded contexts, particularly if those bounded contexts communicate synchronously with each other.

@mahdi5796 3 месяца назад

@@markrichards5014 thanks for explaining. Did you explain the difference between two in any of your books? If so, which one?

@markrichards5014 3 месяца назад

@@mahdi5796 We touch on this in our architecture: the hard parts book.