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
670
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
320
Django Through The Years
andrewgodwin
0
210
Writing Maintainable Software At Scale
andrewgodwin
0
450
A Newcomer's Guide To Airflow's Architecture
andrewgodwin
0
360
How To Break Django: With Async
andrewgodwin
1
730
Taking Django's ORM Async
andrewgodwin
0
730
The Long Road To Asynchrony
andrewgodwin
0
660
The Scientist & The Engineer
andrewgodwin
1
770
Pioneering Real-Time
andrewgodwin
0
430
Other Decks in Programming
See All in Programming
WebAssemblyインタプリタを書く ~Component Modelを添えて~
ruccho
1
830
0から始めるモジュラーモノリス-クリーンなモノリスを目指して
sushi0120
1
280
GitHub Copilotの全体像と活用のヒント AI駆動開発の最初の一歩
74th
7
2.8k
兎に角、コードレビュー
mitohato14
0
110
DynamoDBは怖くない!〜テーブル設計の勘所とテスト戦略〜
hyamazaki
1
200
管你要 trace 什麼、bpftrace 用下去就對了 — COSCUP 2025
shunghsiyu
0
420
Understanding Kotlin Multiplatform
l2hyunwoo
0
260
LLMは麻雀を知らなすぎるから俺が教育してやる
po3rin
3
2.1k
Dart 参戦!!静的型付き言語界の隠れた実力者
kno3a87
0
200
コーディングは技術者(エンジニア)の嗜みでして / Learning the System Development Mindset from Rock Lady
mackey0225
2
490
Infer入門
riru
4
1.5k
대규모 트래픽을 처리하는 프론트 개발자의 전략
maryang
0
120
Featured
See All Featured
The Pragmatic Product Professional
lauravandoore
36
6.8k
Agile that works and the tools we love
rasmusluckow
329
21k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
50
5.5k
What's in a price? How to price your products and services
michaelherold
246
12k
How STYLIGHT went responsive
nonsquared
100
5.7k
Build your cross-platform service in a week with App Engine
jlugia
231
18k
Why You Should Never Use an ORM
jnunemaker
PRO
58
9.5k
How GitHub (no longer) Works
holman
314
140k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
10
1k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.6k
GraphQLの誤解/rethinking-graphql
sonatard
71
11k
Rebuilding a faster, lazier Slack
samanthasiow
83
9.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