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?
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?
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.
Hi Mark. This one is excellent, I highly appreciate. Coupling and cohesion are the roots of all architectural matters.
I agree, which is why I am fascinated with this quantum concept.
@@markrichards5014 Yep, it's really brilliant. Thank you.
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?
That is correct! Because they share a DB synchronously, that puts them in the same quantum
@@markrichards5014 Thank you a lot, totally makes sense. A huge thank you for the great book, btw. :)
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?
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.
@@markrichards5014 thanks for explaining. Did you explain the difference between two in any of your books? If so, which one?
@@mahdi5796 We touch on this in our architecture: the hard parts book.
User interface for ticket creation could use micro front-end/ module federation approach
Correct - and that would help separate the quanta.
very architectural t-shirt 😁😁
RSpec has released its equivalent of ArchUnit
it "depends" do
...
end
Isn't operational reporting quanta depends on data aggregation from other services
Which is async so it makes it separately deployable unit 🎉
@@zxyi9090 That is correct! If it were synchronous, then yes, it would be a single quantum.
❤first comment ❤