[saryant]

> Netflix is strong on eventual consistency, and making services as small as possible. Having tried to build something in that image, holy shit the issue of distributed transactions becomes a nightmare.

Distributed transactions are a sure sign that your service boundaries have been incorrectly drawn.

[forgotpassagan]

Not according to Google :). They actually support and encourage distributed transactions across boundaries.

Imagine all the data Google stores with your user profile across their hundreds of application boundaries. To keep things consistent you would either need to store all profile data in one massive service or support distributed transactions.

The Netflix model is fault tolerance, with every service supporting various failed profile update scenarios. Google just decided to add distributed transactions support to spare all that overhead.