Aside: consistency versus flow-based switching
Thursday, February 04, 2010
4:42 PM
Consistency versus flow-based switching
If you have strong consistency, you don't need flow-based switching, because the distributed object is "always right" about the data about the object, no matter which application instance is contacted next. 
What can go wrong with combining weak consistency and flowless switching? Suppose you purchase a product and a different application instance on a different server instance prints your receipt. What if that instance doesn't see your transaction yet?