Comment by goodpoint
1 day ago
Yes, you are missing the cost of complexity and network calls. You are describing a distributed monolith. It does not help.
1 day ago
Yes, you are missing the cost of complexity and network calls. You are describing a distributed monolith. It does not help.
Not sure I understand. What is a distributed monolith?
I'm not suggesting that the distributed bit is still coupled behind the scenes ( ie via a data backend that requires distributed transactions ) - the interaction is through the interface.
In the end you are always going to have code calling code - the key point is to assume these key calls are simply data passing, not behaviour passing, and that they can fail.
What else is need to make something network friendly? ( I'm suggesting that things like retries, load-balancing etc can be hidden as a detail in the network implementation - all you need to surface is succeed or fail ).