Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Async, Python, and the Future
Search
Andrew Godwin
March 23, 2021
Programming
2
660
Async, Python, and the Future
A keynote I gave at Python Web Conference 2021.
Andrew Godwin
March 23, 2021
Tweet
Share
More Decks by Andrew Godwin
See All by Andrew Godwin
Reconciling Everything
andrewgodwin
1
310
Django Through The Years
andrewgodwin
0
200
Writing Maintainable Software At Scale
andrewgodwin
0
440
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
350
How To Break Django: With Async
andrewgodwin
1
730
Taking Django's ORM Async
andrewgodwin
0
720
The Long Road To Asynchrony
andrewgodwin
0
660
The Scientist & The Engineer
andrewgodwin
1
760
Pioneering Real-Time
andrewgodwin
0
420
Other Decks in Programming
See All in Programming
PHPでWebSocketサーバーを実装しよう2025
kubotak
0
310
状態遷移図を書こう / Sequence Chart vs State Diagram
orgachem
PRO
2
200
新メンバーも今日から大活躍!SREが支えるスケールし続ける組織のオンボーディング
honmarkhunt
5
8.7k
[SRE NEXT] 複雑なシステムにおけるUser Journey SLOの導入
yakenji
0
140
おやつのお供はお決まりですか?@WWDC25 Recap -Japan-\(region).swift
shingangan
0
140
Advanced Micro Frontends: Multi Version/ Framework Scenarios @WAD 2025, Berlin
manfredsteyer
PRO
0
390
システム成長を止めない!本番無停止テーブル移行の全貌
sakawe_ee
1
340
MDN Web Docs に日本語翻訳でコントリビュートしたくなる
ohmori_yusuke
1
130
スタートアップの急成長を支えるプラットフォームエンジニアリングと組織戦略
sutochin26
1
7.2k
Flutterで備える!Accessibility Nutrition Labels完全ガイド
yuukiw00w
0
170
PostgreSQLのRow Level SecurityをPHPのORMで扱う Eloquent vs Doctrine #phpcon #track2
77web
2
580
AI コーディングエージェントの時代へ:JetBrains が描く開発の未来
masaruhr
1
200
Featured
See All Featured
XXLCSS - How to scale CSS and keep your sanity
sugarenia
248
1.3M
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
2.9k
Java REST API Framework Comparison - PWX 2021
mraible
31
8.7k
A Tale of Four Properties
chriscoyier
160
23k
Thoughts on Productivity
jonyablonski
69
4.7k
The Cost Of JavaScript in 2023
addyosmani
51
8.6k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
53k
Testing 201, or: Great Expectations
jmmastey
43
7.6k
How to Think Like a Performance Engineer
csswizardry
25
1.7k
A designer walks into a library…
pauljervisheath
207
24k
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
34
5.9k
How to train your dragon (web standard)
notwaldorf
96
6.1k
Transcript
ASYNC, PYTHON, AND ANDREW GODWIN // @andrewgodwin THE FUTURE
Hi, I’m Andrew Godwin • Django core developer • Worked
on Migrations, Channels & Async • Dabbled with Python async since 2009
None
The Past What is all this async business anyway? The
Present The long road and where we've got to The Future Is there a perfect solution to all this?
The path was forged by other languages And continues to
be - we're all one community in the end
1998 threading module, Stackless Python 2002 Twisted 2006 Greenlets (later
gevent, eventlet) 2008 multiprocessing module 2012 Tulip, PEP 3156 2014 asyncio module 2005 Coroutine-friendly generators (PEP 342)
Threading & Multiprocessing They're concurrency, but not really "async" in
the way we use it now
Twisted The original, and ahead of its time!
Greenlets & Gevent An almost drop-in solution… but it's never
that easy
Generators & Tulip The foundation of our current, cooperative async
1998 threading module, Stackless Python 2002 Twisted 2006 Greenlets (later
gevent, eventlet) 2008 multiprocessing module 2012 Tulip, PEP 3156 2014 asyncio module 2005 Coroutine-friendly generators (PEP 342)
What did we learn? A lot, but not everything.
Let's talk about the present And, of course, asyncio
Asyncio is here, and it's gaining traction Library support! Framework
support!
# Ready when a timer finishes await asyncio.sleep(1) # Ready
when network packets return await client.get("http://example.com") # Ready when the coroutine exits await my_function("hello", 64.2)
Network/timer updates An event loop's flow Select a ready task
Run task Add new tasks to queue await
Coroutines Time →
It is, however, not yet perfect. Turns out, it's a
really hard problem to solve
Everything must cooperate! One bit of synchronous code will ruin
the whole thing.
Can't tell if a function returns a coroutine! There are
standard hints, but no actual guaranteed way
async def calculate(x): result = await coroutine(x) return result #
These both return a coroutine def calculate(x): result = coroutine(x) return result
Can't have one function service both How we got here
makes sense, but it's still annoying sometimes.
You have to namespace async functions I really, really wish
we didn't have to
instance = MyModel.objects.get(id=3) instance = await MyModel.objects.a.get(id=3)
WSGIHandler __call__ WSGI Server WSGIRequest URLs Middleware View __call__ ASGIHandler
__call__ ASGI Server ASGIRequest Asynchronous request path BaseHandler get_response_async BaseHandler get_response URLs Middleware Async View __call__ Django's dual request flows
But, in many ways, the future is here You can
just write full async Python now, and it works pretty well.
So what does the future hold? Apart from, in my
case, a very delicious meal.
Obviously, more library support Databases & common services are still
thin on the ground
Safety, Safety, Safety Async code is HARD. Really hard.
How do we design out silent failure? Deadlocks, livelocks, race
conditions...
How do we prioritise? It's not like you have all
day to add new things.
Horizontal scalability is more important It's the difference between life
and death for a web service.
Long-polling and sockets need async Or your server bill will,
instead, be the death of you
I think we need both Sync and async code both
have their place.
Some things don't need async They're better off a little
slower and safer
Asyncio only benefits IO-bound code Code that thrashes the CPU
doesn't benefit at all
What does this mean for the Web? Our roles are
changing along with our technology
Parallel Queries After all, we're the experts in fetching data
Notifications & Events Polling will absolutely wreck your servers Microservices / API aggregation It's a lot quicker to call those 10 things in parallel
What does this mean for you? You're probably not in
quite as deep as I am
Mixed-mode is coming Django has it, Flask is really close.
Think about your architecture Group things that all do I/O
& requests together, for future parallelisation
Experiment! Take some async code for a spin.
Be the change you want to see. There's a lot
of work to be done, and never enough of us to do it.
Thanks. Andrew Godwin @andrewgodwin // aeracode.org