Sequential execution¶
Category: Foundations · Status: stub
One line: Steps run one after another in a fixed order, each finishing before the next starts: a single total order of events, and the baseline every concurrent program is measured against.
Also called: serial execution, sequential programming.
How it connects¶
flowchart LR
n_concurrency["Concurrency"]
n_sequential_execution["Sequential execution"]
n_concurrency ---|vs| n_sequential_execution
classDef center stroke-width:3px
class n_sequential_execution center
classDef outside stroke-dasharray: 4 3
class n_concurrency outside
- Often confused with: Concurrency
Where to read more¶
- In the books: Hands-On Concurrency with Rust, Brian L. Troutwine — ch. 2, 'Sequential Rust Performance and Testing'
- In the books: Grokking Concurrency, Kirill Bobrov — ch. 2, 'Serial and parallel execution'
- In the books: Multi-Threaded Programming in C++, Mark Walmsley — ch. 1, 'Introduction' → 'Single Threaded Programming'
- In the books: Java Concurrency in Practice, Brian Goetz, Tim Peierls, Joshua Bloch, Joseph Bowbeer, David Holmes, Doug Lea — ch. 9, 'GUI Applications' → 'Why are GUIs Single-threaded?'
- In the books: Python Concurrency with asyncio, Matthew Fowler — ch. 1, 'Getting to know asyncio' → 'How single-threaded concurrency works'
- In the books: Multithreaded JavaScript, Thomas Hunter II, Bryan English — ch. 1, 'Introduction' → 'Single-Threaded JavaScript'
- Notes: sequential programming - sequential functions - sequential platform ↗
- Notes: Sequential Steps ↗
- Reference: Dominik Tornow: Distributed Async Await (NDC talk) ↗