The main concern when you deal with concurrency is shared, mutable state or as Tony Van Eerd put it in his CppCon 2014 talk “Lock-free by Example”: “Forget what you learned in Kindergarten (i.e., stop Sharing).”
I present in theory and praxis proven patterns such as thread-safe storage, strategized locking, thread-safe interface, or guarded suspension to deal with the enemies of thread-safe programming: shared state and mutation.
To synchronize and schedule member function invocations in a concurrent architecture, the classics such as active object, or monitor object provide valuable services.