What are common concurrency pitfalls? [closed]

Answer 1

Concurrency doesn't have many pitfalls.

Synchronizing access to shared data, however, is tricky.

Here are some questions anyone writing shared-data synchronization code should be able to answer:

1. What is InterlockedIncrement?
2. Why does InterlockedIncrement need to exist at an assembly language level?
3. What is read write reordering?
4. What is the volatile keyword (in c++) and when do you need to use it?
5. What is a synchronization hierarchy?
6. What is the ABA problem?
7. What is cache coherency?
8. What is a memory barrier?

"Shared everything" concurrency is an extremely leaky abstraction. Adopt shared nothing message passing instead.