Coroutines, Async/Await, Asyncio and the Pulsar Library
summary
Compares threading, naive multiprocessing (crashes when spawning 10,000 sleeps), Go (~11s) and asyncio, showing concrete code: using asyncio.sleep futures, event loop, yield from in 3.4 and async/await vs yield from in 3.5 beta as built-in coroutine types; shows Tornado integration, aioredis/aiopg-style libraries, and websockets working without extra threads. Describes Pulsar as an actor-based Pulsar framework layered on asyncio (actors addressed by name, multiprocessing via actors), notes Docker for Python 3.4/3.5 testing and current sparse documentation.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 1:17Understanding async IO
- 4:17Why use asynchronous code?
- 5:49Concurrency comparisons
- 10:07Async IO implementation
- 12:39Async and await syntax
- 14:06Benefits of the standard library
- 17:45Ecosystem and libraries
- 21:35Real-world web example
- 27:22Pulsar and the actor model
- 33:04Q&A and concluding remarks
related talks
01h 29mStandardised Coroutine Concurrency in Python 3
50mUsing Asyncio in Python 3
31mA Really Gentle Introduction to Asyncio
23mPractical usage of asyncio
59mGet to grips with asyncio in Python 3
40mAdvanced asyncio: Solving Real-world Production Problems
32mAdvanced asyncio: Solving Real-World Production Problems
57mFear and Awaiting in Async: A Savage Journey to the Heart of the Coroutine Dream