BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//pyconde-pydata-2026//speaker//3CXHP7
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-pyconde-pydata-2026-TRGQTL@pretalx.com
DTSTART;TZID=CET:20260416T113500
DTEND;TZID=CET:20260416T122000
DESCRIPTION:Open table formats have *almost* freed us from vendor lock-in. 
 They form a critical building block of the modern\, composable data stack.
  The most prominent open table format is Apache Iceberg - not only because
  of its storage layout\, but also due to its REST catalog specification. I
 ceberg has gained significant traction through a recent stream of feature 
 announcements from the community itself\, major cloud providers like AWS\,
  and data platform leaders such as Snowflake and Databricks.\n\nBut cuttin
 g through the hype: how does Iceberg actually perform in the real world if
  you are *not* Netflix or Apple which are capable of *Building Your Own Sn
 owflake* (BYOS)? Can you realistically migrate from legacy solutions to Ic
 eberg and enjoy all its promises without tradeoffs?\n\nThat\, of course\, 
 is a rhetorical question. Some even argue that Iceberg got parts of the sp
 ecification fundamentally wrong!?!\n\nCurious? Join me for another episode
  of Open Table Formats in the Wild™. Expect a practical look at the curr
 ent state of Apache Iceberg and Apache Parquet\, alongside a gentle introd
 uction to DuckLake and Vortex as promising contenders for table and file f
 ormats\, respectively.
DTSTAMP:20260412T141856Z
LOCATION:Titanium [2nd Floor]
SUMMARY:Open Table Formats in the Wild™ - Reloaded: Vortexing Ducks over 
 Floating Icebergs - Franz Wöllert
URL:https://pretalx.com/pyconde-pydata-2026/talk/TRGQTL/
END:VEVENT
END:VCALENDAR