If you don’t share, no data races can happen. Not sharing means that your thread works on local variables. This can be achieved by copying the value, using thread-specific storage, or transferring the result of a thread to its associated future via a protected data channel.
There are many well-established patterns used in the concurrency domain. They deal with synchronization challenges such as sharing and mutation but also with concurrent architectures. Today, I will introduce and dive deeper into them in additional posts.
My next mentoring program, “C++20: Get the Details”, starts in July. Registration will open in June.
Event-driven applications, such as GUIs or servers, often apply the architecture pattern Reactor. A Reactor can accept multiple requests simultaneously and distribute them to different handlers.
The Model-View-Controller (MVC) is one of the classic architectural patterns from the book “Pattern-Oriented Software Architecture, Volume 1“. It addresses interactive applications with a flexible human-machine interface.
The Broker Pattern structures distributed software systems that interact with remote service invocations. It is responsible for coordinating the communication, its results, and exceptions.
Last Monday, I published an article on Heise, “Mangel an Fortbildung: Warum die Kulturlosen keine Chance haben” that got almost 300 comments. Here is my English translation of this article.
The Pipes-and-Filters architecture pattern describes the structure of systems that process data streams.
The layers pattern splits a task into horizontal layers. Each layer has a specific responsibility and provides a service to a higher layer.