Mark Little provides advice on when it is not recommended to use transactions and how to use transactions with Web Services, NoSQL, REST and mobile infrastructures.
Sean Cribbs compares ACID with BASE, explaining the virtues and tradeoffs of eventually consistent systems and what developers should know in order to feel comfortable working with EC systems.
Jags Ramnaraya presents SQLFire and how SQL can be used for modern data stores backing online highly scalable applications by using a different consistency model and sharing nothing persistence.
Justin Sheehy explains why a paradigm shift is necessary when dealing with large concurrent distributed systems and what are some of their requirements: no global state is shared, ACID no longer works but rather BASE and CAP, getting rid of RPC and using protocols over APIs instead, prepare for failure, degradation, understanding the harvest-yield balance, and using measurement.
This talk describes the constraints of connected systems design and presents common design patterns to address some of the challenges developers will face as they spend more time connecting services and components instead of developing new ones. Along the way he asks: Is coupling really so bad? Why is REST popular? Do we need distributed transactions?