BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-cz-2025//speaker//3JCL9A
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-cz-2025-QQY9AK@pretalx.devconf.info
DTSTART;TZID=CET:20250612T123000
DTEND;TZID=CET:20250612T130500
DESCRIPTION:Within an event-driven\, microservices architecture there's oft
 en a big gap between a web component that relies on some data\, and the ev
 ent data itself. There will usually be several services in the middle\, fr
 om multiple APIs\, databases\, distributed caches etc. Building and updati
 ng that web component might mean touching many codebases and coordinating 
 across many teams. This can be slow and hamper experimentation. What if...
  we bring that raw event data right into the browser\, making it\, in effe
 ct "event driven"? That web component can be developed and iterated on at 
 lightning speed. New components can be built without the need for new endp
 oints. With access to the raw data\, frontend developers suddenly have the
  freedom to explore new\, bold ideas without fear of the upstream complexi
 ty.
DTSTAMP:20260611T154038Z
LOCATION:D0206 (capacity 154)
SUMMARY:Event Driven Frontends: What\, Why and How - Matthew Cox
URL:https://pretalx.devconf.info/devconf-cz-2025/talk/QQY9AK/
END:VEVENT
END:VCALENDAR