Event-Sourcing basic example app

Aim: learn basics of event-sourcing pattern and its caveats.

This project builds on example from presentation from Mathias Verraes - Practical Event Sourcing.

Learning matherial

Bellow is learning matherial that I've used to dive into event DDD (and its implementations) deeper.

DDD: Domain Driven Design

I've put DDD in it's own section because DDD is more analysis process then collection of structural patterns.

• Jimmy Bogard: Domain Driven Design: The Good Parts
• Jimmy Bogard: Crafting Wicked Domain Models
• book: Eric Evans: Domain-Driven Design - Tacking Complexity in the Heart of Software (book; read especially bounded context capture)
  • Eric Evans: Tackling Complexity in the Heart of Software (10 years later; explains nicely how to read the book)
• Greg Young: A Decade of DDD, CQRS, Event Sourcing

Case studies

• Lufthansa case study

Learning the Technical Stuff

This sections actually describes how people are implementing their domains discoved by using DDD. Be careful applying patters bellow blindly.

Event Sourcing + CQRS

Alternative implementation of domain model persistence layer which stores complete history of all events that happend to domain in past.

• Greg Young's Event sourcing class + Greg Yong's CQRS documents (circa overview of course)

• Greg Young's hi-level overview of CQRS/DDD

• Querying Event Streams (wow!)

• SzymonPobiega's DDD reading list

• Greg Young's full and up-to-date DDD/CQRS/EventSourcing class

• Mathias Verraes' elaborate on domain events - Domain Events allow you to segregate the models of different systems

• unknown's Domain Driven Design Through Onion Architecture

• CQRS.nu

• DDD Community

• Tip: Try to watch some microservices / stream processing videos. You will see unxpected similarities.

(The structural part of) DDD in PHP

• William Durand: DDD with Symfony2:
  • Folder Structure And Code First
  • Making Things Clear
  • Basic Persistence & Testing
• Jan Kuchar's second sanbox
• DDDinPHP

Message Buses / libraries

• Prooph (cool one!)
  • super flexible
  • library: ability to mix&match
  • well designed
  • support for snapshotting
  • unfortunately does not support Sagas yet! (contribution?)
  • up-casting is strange: why it is not JIT up-cast? http://getprooph.org/event-store/upcasting.html
  • Nested transaction? http://getprooph.org/event-store-bus-bridge/transaction_manager.html
• broadway
  • feature richer
  • you have to use all (single package)
  • more like a framework then library (overkill?)
  • looks like a some's project by product
  • experimental support for process managers
• Predaddy
• EventCentric.Core
• litecqrs-php
• Buttercup.Protects - A PHP library for building Aggregates that protect business invariants, and that record Domain Events.
  • Nice explanation of event-sourcing principles on a richly commented simple example code.

Process Managers / Sagas (the same thing!)

• Jonathan Oliver: Sagas with Event Sourcing - first part, second part
• Jonathan Oliver: Sagas, Event Sourcing, and Failed Commands
• Udi Dahan: Saga Persistence and Event-Driven Architectures

Examples

• Mathias Verraes: Buttercup.Protects is a PHP library for building Aggregates that protect business invariants, and that record Domain Events.
• EventSourcing at BlaBlaCar + Matthieu Moquet: CQRS & Event Sourcing
• GitHub: example applications written with CQRS/event sourcing pattern

Notes / TODOs

• How to make proper relation between Product and Basket?
  • Answer: Analyse bounded contexts. (probably in most domains use two separate AggregateRoots)
• How to access product name when product-related event occurs - aggregate does not expose any state?! (should I access read model from write model?)
  • Answer: Access read side if needed or use heavy events.
• If aggregate produces event but it does not change state in any way, should it have empty apply() method for this event or should framework just skip this event. (this can lead into hard discoverable typo errors)
  • Answer: I would prefer to hot have this methods in aggregate and have some kind of static analysis check for method name and type consistency (in PHP which does not support method overloading).
• Is there any point of adding events when loading from history into object "recoded events"?
  • Answer: No, if you load them there, they will be persisted once more / there will be need for merge proccess.