The sync-vs-async decision framework
P32.sync-vs-async.01 · Audience: guest, it-ml, language-pro · Prerequisites: Threads vs processes & the GIL
You now have three tools — threads, processes, and (next pillar) asyncio. The senior skill is choosing between them, and knowing when to reach for none of them. This short track builds the decision framework and bridges into P33 · Asyncio & Coroutines.
ⓘ Concept: CPU-bound or I/O-bound?
Why it matters — Almost every concurrency decision falls out of this single classification — get it right and the tool chooses itself.
Ask the mentor about this module
Ask a question about this content. The mentor explains and grounds its answer in what you are studying; asking is recorded as a learning signal, not a grade.
Keeping your files on this device
Off by default. The mentor always gets your file; this only decides whether your own copy stays here. Copies live in this browser only - they do not follow you to another device, and clearing site data removes them.
🎓 Practice ladder
1 graded rung · ~8 minPut it in words: build the decision table an interviewer would accept, and set up the bridge into asyncio.
Rung 1 — sync vs async, and how to choose (interview)
Loading exercise…
That framework — classify the work, then pick the tool — is what carries you into P33, where asyncio turns "wait on thousands of things at once" into ordinary code.
My notes on this module
Loading your notes...
Where next?
Go up a level