Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Cyprien Noel discusses distributed transactional memories along with ObjectFabric, a Java server based on eXtensible Software Transactional Memory, an OS library for concurrent and distributed apps.
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.
Martin Thompson and Michael Barker talk about building a HPC financial system handling over 100K tps at less than 1ms latency by having a new approach to infrastructure and software. Some of the tips include: understand the platform, model the domain, create a clear separation of concerns, choose data structures wisely, and run business logic on a single thread.
Bill Burke shows how to use REST to create interfaces to middleware services – messaging, transactions, workflow, security – in order to have RESTful enterprise SOA implementations, and what are the limitations of REST.
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?
This presentation, from QCon SF 08, analyzes real world projects where using explicit state transition models was made and the many interesting modeling/architectural possibilities that arose from the decision. Along the way, the IMIS system and its performance is linked to explicit state transition modeling.
Betfair is the world's largest betting exchange with a transaction volume the equivalent of over half the combined equity trading volume of every major stock exchange in the world. In response to an increase in transaction volume coupled with a decrease in value per transaction, Betfair launched a number of initiatives to dramatically increase transaction processing capacity and reduce cost.
In this presentation from the JVM Languages Summit 2008, David Chase discusses Fortress, a Fortran-based highly parallel programming language. Topics covered include the origins of Fortress, mathematical syntax, the challenges of running on the JVM, parsing, work stealing, transactions, continuations, problems with blocking, the type system, type mapping, multiple dispatch and profiling.
In this presentation from QCon London, William Soo and Meeraj Kunnumpurath discuss the Voca transaction processing system architecture, the previous Mainframe-based architecture, architectural challenges and requirements, the new Spring and J2EE-based architecture, upcoming challenges for Voca, and technologies to watch for in the future.
A core part of Spring's middle tier support is the transaction management support. This session presents several interesting "mission critical" cases and shows you how to properly handle them using transactions driven by Spring 2. You'll learn the ins-and-out of the "dark art" that is transaction management within a high-volume mission-critical JEE application.