BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//pyconde-pydata-2025//talk//7PDARV
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-2025-7PDARV@pretalx.com
DTSTART;TZID=CET:20250424T142000
DTEND;TZID=CET:20250424T145000
DESCRIPTION:As we develop business critical software\, we often need to rel
 y on external APIs to get the job done. And all services are not born equa
 l: although the ideal world would provide well operated APIs with over-met
  service levels\, the real world is usually way worse than that. Timeouts\
 , HTTP errors\, cascading failures\, unclear or changing contracts\, appro
 ximate protocol implementations ... And even the oh-so-human bad faith whi
 le trying to pinpoint the root cause... Most of us have written hacks to h
 andle commonly seen failures\, from the quick and dirty implementation to 
 well thought resilience patterns implementation\, but this is usually hard
  to do correctly\, and rarely a business priority to invest the correct am
 ount of time and money on the topic. We'll present the options\, both incl
 uding direct dependencies (not framework dependant\, although some familie
 s can emerge (async/sync ...)) and including a service/proxy based approac
 h.
DTSTAMP:20260511T113357Z
LOCATION:Hassium
SUMMARY:Writing reliable software while depending on hazardous APIs - Romai
 n Dorgueil
URL:https://pretalx.com/pyconde-pydata-2025/talk/7PDARV/
END:VEVENT
END:VCALENDAR