Greg Young discusses how to use events to store data, and how testing, versioning and performance are impacted by an event-centered model.
Richard Tibbetts discusses Complex Event Processing in the context of High Frequency Trading and the advantages of using high level DSLs, followed by the case study of a system built with StreamBase.
Ian Bond presents the development of a trade flow event-driven architecture, providing the background of futures trade, the domain and the solution, sharing some of the lessons learned along the way.
Stefan Norberg introduces Domain Event-Driven Architecture, how it helps SOA, and how it has been used by Unibet to make its architecture less coupled, resulting in better performance and scalability. Norberg offers practical advice, presenting technical details of the technologies used: JMS, XML, JSON, Google Protocol Buffers, ActiveMQ and Spring.
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, recorded at QCon San Francisco, ThoughtWorks' Ian Robinson explains how a RESTful HTTP approach can be applied in an Enterprise project. He makes use of many of the techniques that make HTTP a powerful protocol, including caching, hypermedia, and the use of standard formats such as Atom Syndication for event notification.
Ian Cartwright presents some of his work (developed with Martin Fowler) on Event Patterns, including: Event Sourcing, Event Collaboration, Parallel Model, and Retroactive Event. These patterns can be used in scenarios where a sequence of domain model changes may need to be recorded, reversed, corrected, or simply observed.