exercises

Exercises: Asynchrony

Theoretical exercises:

• Q1: Callbacks vs Futures
• Q2: Concurrency vs. Parallelism
• Q3: Asynchronous cache

Practical exercises:

• Q4: Reliable document providers
• Q5: Testing

The solutions are available.

Ideas for your own projects:

• Think of which operations in your system should be async, particularly around I/O
• If you provide a user interface, show a progress bar while async operations are ongoing
• If you use programming languages that support them, try out features such as async/await or coroutines