> Communication with other SCSs or 3rd party systems is asynchronous wherever possible. Specifically, other SCSs or external systems should not be accessed synchronously within the SCS's own request/response cycle. This decouples the systems, reduces the effects of failure, and thus supports autonomy.
This is some seriously bad advice. First, asynchronous code is much harder to get right, from a correctness point of view. Second, it is much more complex both in the technical aspects as well as in cognitive complexity. Then, simply by virtue of being asynchronous they don't become decoupled as suggested in the quote.
I urge everyone to think for themselves before following the advice in this so-called "architecture".
This is some seriously bad advice. First, asynchronous code is much harder to get right, from a correctness point of view. Second, it is much more complex both in the technical aspects as well as in cognitive complexity. Then, simply by virtue of being asynchronous they don't become decoupled as suggested in the quote.
I urge everyone to think for themselves before following the advice in this so-called "architecture".