2 ms·
Often you don't worry about transactions across services. I know that someone will say we have to have them. In such cases, fine worry about them. In everything
by virmundi 11y ago
Often you don't worry about transactions across services. I know that someone will say we have to have them. In such cases, fine worry about them. In everything else, either isolate the write side of a transaction in one service or don't require them.
- paulddraper 11y ago"don't require them".... Transactionlity is principally dicated by the requirements to the architecture design, not the other way around. " isolate to one service " Yep, a single service with a single database, as mentioned. My point here, like the earlier one, is that there are a lot of situations where multiple services don't fit the domain. In fact, very many, given the extreme complexity around transactions.