Event-Driven asyncio: A Case Study of Trio's API
summary
Case study of a robot decision engine that runs on over 100,000 units with constrained CPUs MCUs and sensors shows Python async delivering single‑thread concurrency while saving resources The team compares trio and trio-util with anyio and asyncio and implements a concrete Value combinator API that watches websocket inputs composes values and cancels cleanly The implementation runs in production handles dozens of sensors per robot and replaces ad hoc callbacks with structured concurrency
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:14Python for robot engines
- 3:08Case study overview
- 4:11Python and Trio for async
- 6:43Handling multiple inputs
- 7:48Watching multiple inputs demo
- 10:01Trio's Value API explained
- 13:01Event API limitations
- 14:03Closing remarks
related talks
47mTaking Asynchronous Python to the Next Level Using Trio
37mTaking Asynchronous Python to the Next Level Using Trio
32mTrio: Async concurrency for mere mortals
32mAdvanced asyncio: Solving Real-World Production Problems
50mUsing Asyncio in Python 3
27m"Python’s tale of concurrency"
24mA Crash Course in Python 3's asyncio
26mWhy I reimplemented Trio in a game engine