Greg Young discusses unexpected use cases and possible usages of the Event Store.
Peter Ledbrook overviews several application architectures that can be done in Grails: MVC plus a DB back-end and a service layer, single-page, and event-based back-end.
Chris Riccomini discusses: Samza's feature set, how Samza integrates with YARN and Kafka, how it's used at LinkedIn, and what's next on the roadmap.
Jessica McKellar introduces Twisted, a Python event-driven networking engine, and explaining several design concepts used: deferred API, transport/protocol separation, and plug-in infrastructure.
Ward Cunningham keynotes on how Events, Sockets, CORS, Closures, SVG, DSLs, Canvas, EC2 and Raspberry Pi contribute to a new type of wiki, a federated one.
Paul Buhler provides insight into the development and application of a semantically grounded version of the Workflow Management Coalition's Business Process Analytics Format (BPAF) specification.
James Lewis tells the story of building a resource oriented, event driven system out of applications about 1000 lines long.
Uri Cohen discusses several types of queues with their pros and cons used in financial and trading industries for highly parallelized data processing.
Yves Reynhout discusses event sourcing and storage, demoing implementing a conceptual event storage model on top of AWS Storage and Azure Storage Services.
Martin Thompson discusses achieving high availability by using an event sourced architecture in which changes of the system’s state is captured as a sequence of events.
Donald Belcham presents the Event Aggregator pattern and the event problems it solves: tight coupling, refactoring difficulty, object chaining, memory leak, showing how to build one.
Greg Young discusses how to use events to store data, and how testing, versioning and performance are impacted by an event-centered model.