The need for concurrency
Most of the time, when we are building fairly simple applications, we do not require concurrency. Simple, sequential programming works just fine, in which one step executes after the completion of another. But as application use cases become more and more complex, and there are an increased number of tasks that can easily be pushed into the background to improve the application's user experience, we end up revolving around the concept of concurrency.
Concurrency is a different beast in itself and makes the task of programming much more complex. But regardless of the added complexity, concurrency also brings a lot of features to improve the user experience of applications.
Before we dive into the question of why we ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access