BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2024//speaker//AU3L
 9P
BEGIN:VTIMEZONE
TZID:Europe/Prague
BEGIN:DAYLIGHT
DTSTART:20230709T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20231029T030000
RDATE:20241027T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240331T030000
RDATE:20250330T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Event Sourcing From The Ground Up - Sebastiaan Zeeff\, Ravi Selker
DTSTART;TZID=Europe/Prague:20240708T093000
DTEND;TZID=Europe/Prague:20240708T110000
DTSTAMP:20261116T062357Z
UID:pretalx-europython-2024-U7UMBE-0@programme.europython.eu
DESCRIPTION:We often think about data in terms of storing the current stat
 e of our models. If a chess player moves a piece\, we update the state of 
 the board and persist it. This makes it easy to query the current state of
  the game\, but also poses some challenges: How do we know which moves led
  up to the current state? And how do we ensure that the state remains cons
 istent\, even in a distributed system?\n\n**Event Sourcing** takes a diffe
 rent approach to storing state. Instead of storing the current state as-is
 \, we store the *sequence of events* that led to the current state. If we 
 need to know the current state\, we can replay this immutable record of ev
 ents to reconstruct it. Not only does this give us an immutable audit log
 \, this also promotes loose coupling and enables optimistic concurrency.\n
 \nIn this tutorial\, we are going to build an “Event Sourcing”-based b
 ackend for a simple Connect 4 game. Rather than using a framework that abs
 tracts away some of the core principles\, we are going to implement the me
 chanisms ourselves to help us understand the core principles.\n\n### Outli
 ne\n- Introduction to Event Sourcing and Domain-Driven Design\n- Modeling 
 the events in our game\n- Implementing our first events and our aggregate
 \n- Reconstructing state from events\n- Persisting the events\n- Beyond th
 is tutorial + Q&A\n\n### Audience & Preparation\nThis tutorial is for you 
 if you’re interested in Event Sourcing but don’t have any real experie
 nce with it yet. We do expect you to have at least an intermediate level i
 n Python.\n\nDo make sure to bring your laptop\, **with the following tool
 s installed**:\n- Python 3.12\n- Docker (free-to-use for educational purpo
 ses)\n- Git\n- Your favorite editor\n\nAfter you've installed everything o
 n your laptop\, clone [the repository](https://github.com/Ordina-Group/pyt
 hon-event-sourcing-tutorial) and follow the instructions in the README.md 
 to set up the project.
LOCATION:Club H
URL:https://programme.europython.eu/europython-2024/talk/U7UMBE/
END:VEVENT
BEGIN:VEVENT
SUMMARY:Event Sourcing From The Ground Up - Sebastiaan Zeeff\, Ravi Selker
DTSTART;TZID=Europe/Prague:20240708T111500
DTEND;TZID=Europe/Prague:20240708T124500
DTSTAMP:20261116T062357Z
UID:pretalx-europython-2024-U7UMBE-1@programme.europython.eu
DESCRIPTION:We often think about data in terms of storing the current stat
 e of our models. If a chess player moves a piece\, we update the state of 
 the board and persist it. This makes it easy to query the current state of
  the game\, but also poses some challenges: How do we know which moves led
  up to the current state? And how do we ensure that the state remains cons
 istent\, even in a distributed system?\n\n**Event Sourcing** takes a diffe
 rent approach to storing state. Instead of storing the current state as-is
 \, we store the *sequence of events* that led to the current state. If we 
 need to know the current state\, we can replay this immutable record of ev
 ents to reconstruct it. Not only does this give us an immutable audit log
 \, this also promotes loose coupling and enables optimistic concurrency.\n
 \nIn this tutorial\, we are going to build an “Event Sourcing”-based b
 ackend for a simple Connect 4 game. Rather than using a framework that abs
 tracts away some of the core principles\, we are going to implement the me
 chanisms ourselves to help us understand the core principles.\n\n### Outli
 ne\n- Introduction to Event Sourcing and Domain-Driven Design\n- Modeling 
 the events in our game\n- Implementing our first events and our aggregate
 \n- Reconstructing state from events\n- Persisting the events\n- Beyond th
 is tutorial + Q&A\n\n### Audience & Preparation\nThis tutorial is for you 
 if you’re interested in Event Sourcing but don’t have any real experie
 nce with it yet. We do expect you to have at least an intermediate level i
 n Python.\n\nDo make sure to bring your laptop\, **with the following tool
 s installed**:\n- Python 3.12\n- Docker (free-to-use for educational purpo
 ses)\n- Git\n- Your favorite editor\n\nAfter you've installed everything o
 n your laptop\, clone [the repository](https://github.com/Ordina-Group/pyt
 hon-event-sourcing-tutorial) and follow the instructions in the README.md 
 to set up the project.
LOCATION:Club H
URL:https://programme.europython.eu/europython-2024/talk/U7UMBE/
END:VEVENT
END:VCALENDAR
