#423 About Event Sourcing
returning guest Johan Haleby, Midsummer pole dancing in Sweden, domain events as facts and decisions that cannot be undone, domain events understandable by business people, event sourcing as storing a list of facts instead of the current state, deriving state from events to make new decisions, storing events vs event sourcing, snapshotting as a technical optimization applied only when needed, closing the books as a domain oriented alternative to snapshotting, tractors returning to the garage as a natural end of a business session, streams per aggregate and reading only the events needed for a decision, commands, deciders and aggregates enforcing business invariants, consistency per farm instead of global consistency, Kafka Streams cascading low-level GPS events into speed, direction and fuel consumption events, translating technical events into business events, Kafka Streams joins and tables on demand as a reversed database, AWS Lambda durable functions as primitive event sourcing per stream, low-level UI events like mouse moved vs business events like player joined game, event sourcing per bounded context, reactive programming vs event sourcing streams, CQRS as an optional addition to event sourcing, read your own writes and Eventual Consistency of read models, BASE vs ACID, a last updated timestamp as a business solution for stale views, writing to PostgreSQL and reading from Elasticsearch, optimistic locking for concurrent decisions, write side vs read side and subscriptions to committed events, Kafka as event streaming platform, not an event store, in-memory event sourcing without distribution, IoT battery state of charge events and notification deciders, Java Flight Recorder events as an observability use case, bank accounts and state transitions as the classic event sourcing use case, events as stories easier to reason about than table relationships, decoupling and extensibility with events, replaying Kafka topics for new microservice versions, storing events in Amazon DynamoDB or with Amazon S3 conditional writes and consistency guarantees per aggregate, events generated by deciders rather than by commands, a future episode about the Occurrent library
Johan Haleby on twitter: @johanhaleby