Dan Sabadis

The main focus in the IT recruitment process goes towards finding the people with the best technological (and abstract reasoning) skills. Rightfully so, these technical capabilities are THE necessary prerequisite for any good employment in our industry. At the same time, the big employers are also oriented, in their hiring strategy, towards searching and matching the best "characters" to a particular advertised position. This is understandable as the big companies are more stable than the start-ups, so the large organizations will invariably put more emphasis on long-time stability than on short-term outstanding results. That's why the corporate hiring staff usually has two main approaches.

In the previous article we laid out the foundation of what multithreading is and described the pillar of asynchronous programming in .Net, namely the IAsyncResult interface. We also provided a brief history of the evolution of the .Net multithreading abstractization, starting with the Thread class and ending with the async-await pattern (and keywords). In this article we will elaborate on the topic, giving detailed .Net thread synchronization examples, focusing on the two modes the CPU is spending time, in any modern operating system: the user-mode and the kernel-mode. As usual, we start with the definitions.

Today we will focus on the “difficult” subject of multi-threading in a big enterprise environment. Because my previous experience was anchored in the .Net Framework, we chose to provide the examples from the C\# language, but the very same concepts, classes and abstractions described below have an almost word-to-word equivalence in Java.