Re:Analysis of Software Architectures
by amelius on Saturday January 09, 2016 @01:58PM
(#10872388)
I guess that not just the joins become more difficult in a partitioned system, but especially transactions. Maintaining transactional consistency across multiple services seems to me like a nightmare. Even writing tests that address consistency could be very difficult.
[ Parent
| on HN ]
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.
Re:Analysis of Software Architectures
by paulddraper on Saturday January 09, 2016 @10:40PM
(#10874042)
"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.
And it's not a coincidence NoSQL systems often punt on joins and transactions in order to scale. Both are really hard to make both correct and efficient in a distributed environment.