Why concurrency: throughput and latency
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
state what concurrency buys and what it costs.
Planned topics
- Throughput: work finished per second. Latency: time for one piece of work.
- Waiting on I/O (database, HTTP) wastes a thread unless other work runs meanwhile.
- Concurrency means tasks in progress together; parallelism means running at the same instant on several cores.
- Costs: complexity, shared-state bugs, context switches, memory per thread.
- Amdahl's law: the serial part limits speed-up.
Draft outline details
Demonstration
timeline: three 200 ms supplier calls sequentially (600 ms) vs concurrently (about 200 ms).
Check your understanding
Which concurrent work gains most: CPU-bound or I/O-bound?
Show answer
I/O-bound, as waits overlap; CPU-bound is limited by cores.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.