BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//programme.europython.eu//europython-2026//speaker//R8WFX
 V
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-QT97WA@programme.europython.eu
DTSTART;TZID=CET:20260715T104500
DTEND;TZID=CET:20260715T113000
DESCRIPTION:Python systems rarely fail because of raw performance limits.\n
 \nThey fail because the architecture does not scale with the team.\n\nAs s
 ervices grow\, coordination overhead increases. Shared databases create im
 plicit coupling. API contracts become political boundaries. Async workflow
 s leak across domains. Meetings multiply to compensate for structural flaw
 s.\n\nInstead of adding process\, we should redesign architecture.\n\nThis
  talk explores how Python system design directly determines team scalabili
 ty.\n\nUsing real-world backend systems built with FastAPI\, asyncio\, gRP
 C (grpcio)\, PostgreSQL\, Redis\, Docker\, we will examine how architectur
 al decisions shape organizational complexity.\n\nTopics include:\n	•	Dom
 ain boundaries in Python services and their impact on ownership\n	•	Data
 base-per-service vs shared schemas\n	•	REST vs gRPC as team contracts\n	
 •	Monorepo vs polyrepo trade-offs in multi-service Python ecosystems\n	
 •	Contract testing and schema evolution\n	•	Observability as an interf
 ace between teams\n	•	Async workloads and cross-service backpressure\n	
 •	When microservices increase coordination cost instead of reducing it\n
 \nRather than promoting a single architecture style\, this session introdu
 ces a framework for evaluating whether a design reduces or amplifies team 
 cognitive load.\n\nAttendees will leave with:\n	•	Criteria for defining 
 service boundaries that align with ownership\n	•	Patterns for reducing c
 ross-team friction through architectural design\n	•	Warning signs that a
 rchitecture is becoming a coordination bottleneck\n	•	Practical techniqu
 es for evolving Python systems without multiplying process\n\nThis talk is
  intended for experienced Python engineers\, architects\, and technical le
 aders responsible for systems that must scale both technically and organiz
 ationally.
DTSTAMP:20260524T121707Z
LOCATION:Conference Hall Complex (S4)
SUMMARY:Scaling Python Systems by Designing Team-Aware Architecture - Ivan 
 Markeev
URL:https://programme.europython.eu/europython-2026/talk/QT97WA/
END:VEVENT
END:VCALENDAR