BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//talk//ZRWENU
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-europython-2026-ZRWENU@programme.europython.eu
DTSTART;TZID=CET:20260715T152500
DTEND;TZID=CET:20260715T155500
DESCRIPTION:APIs development start simple\, feel fast\, and ship quickly. T
 hen the API grows: more endpoints\, more traffic\, more data\, and suddenl
 y performance becomes unpredictable. Latency creeps in\, async code blocks
  without anyone noticing\, and every new feature feels a little riskier to
  add.\n\nThis talk is about building Python APIs that stay fast *as they e
 volve*.\n\nWe’ll look at where performance issues really come from in re
 al-world APIs: request lifecycle overhead\, hidden blocking calls\, depend
 ency injection costs\, serialization\, and poorly scoped middleware. Inste
 ad of chasing micro-optimizations or benchmark numbers\, we’ll focus on 
 design decisions that make performance predictable.\n\nUsing Litestar as a
  concrete example\, you’ll see how explicit control over routing\, depen
 dencies\, and async execution helps avoid common performance traps. We’l
 l walk through realistic API patterns and show how to structure handlers a
 nd dependencies so performance problems don’t slowly accumulate.\n\nYou
 ’ll leave with practical techniques you can apply immediately\, whether 
 you’re building a new API or maintaining one in production. Even if you 
 don’t use Litestar today\, the design principles in this talk will help 
 you reason more clearly about performance in any Python API.
DTSTAMP:20260524T130702Z
LOCATION:Chamber Hall A (S3A)
SUMMARY:Designing Performant APIs with Litestar - Julien Courtès\, Cody Fi
 ncher
URL:https://programme.europython.eu/europython-2026/talk/ZRWENU/
END:VEVENT
END:VCALENDAR