~/talk

Migrating to an Event Sourced system

Talkat The Conf 2019 · 2019-10-23..10-24
links:none on file
slides:none on file

Real estate app experiments with event sourcing but stops short of full migration: backend remains PostgreSQL while teams prototype an event log, try Elixir + Phoenix + Absinthe (GraphQL), adopt commanded CQRS library (pre-1.0), and convert numeric IDs to UUIDs to generate commands outside the DB. Tests and coexistence of old relational repo plus event repo prove painful, many features balloon to dozens of files and hundreds of lines, eventual consistency and aggregate modelling cause surprises, and outcome is a partial proof-of-concept that teaches DDD, event storming and where to apply event sourcing later.

AI-written summary · about

  1. 0:00Introduction and background
  2. 2:09Why event sourcing
  3. 9:22Event sourcing concepts
  4. 17:48Benefits of event-driven systems
  5. 20:37How to implement event sourcing
  6. 26:46Challenges in migration
  7. 29:41Why we didn’t migrate
  8. 30:26Lessons learned
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.