Skip to main content

C# : Interview questions (41-45)


 Questions :

  • What is the purpose of the Thread class?
  • Explain the difference between a thread and a process.
  • How do you synchronize threads in C#?
  • What is deadlock in multithreading?
  • What is a mutex?

Answers :

Purpose of the Thread Class:

The Thread class in C# is used to create and control threads, which are independent sequences of execution within a process. Threads allow multiple tasks to execute concurrently, enabling parallelism and multitasking in applications. The Thread class provides methods to start, pause, resume, and terminate threads, as well as facilities for thread synchronization and coordination.

Difference between a Thread and a Process:

  • Thread:
    • A thread is the smallest unit of execution within a process.
    • Threads within the same process share the same memory space and resources, including code, data, and file handles.
    • Threads are lightweight compared to processes and have less overhead when switching between them.
    • Threads can communicate and synchronize with each other directly.
  • Process:
    • A process is an instance of a running application or program on a computer.
    • Processes have their own memory space and resources, including code, data, and file handles, which are isolated from other processes.
    • Processes are heavyweight compared to threads and have more overhead in terms of memory and system resources.
    • Processes communicate with each other using inter-process communication (IPC) mechanisms.

Synchronizing Threads in C#:

Thread synchronization in C# is achieved using synchronization primitives such as locks, monitors, mutexes, and semaphores. These mechanisms prevent multiple threads from accessing shared resources concurrently and ensure thread safety.

    object lockObject = new object();
    
    lock (lockObject)
    {
        // Critical section: Access shared resources
    }
    

    In this example, a lock statement is used to synchronize access to a critical section of code by acquiring a lock on the lockObject.

    Deadlock in Multithreading:

    Deadlock is a situation in multithreading where two or more threads are blocked indefinitely, waiting for each other to release resources that they need to proceed. Deadlocks typically occur when multiple threads acquire locks on shared resources in different orders, leading to a circular dependency.

    lock (lockObject1)
    {
        lock (lockObject2)
        {
            // Code that accesses resources protected by lockObject1 and lockObject2
        }
    }
    

    In this example, if another thread acquires locks on lockObject2 and lockObject1 in the opposite order, a deadlock may occur if both threads try to acquire locks simultaneously.

    Mutex:

    A mutex (short for mutual exclusion) is a synchronization primitive that provides exclusive access to a shared resource. Unlike locks, which are tied to a specific thread or process, mutexes can be used to synchronize access across multiple threads or processes.

    using System.Threading;
    
    Mutex mutex = new Mutex();
    
    mutex.WaitOne(); // Acquire the mutex
    try
    {
        // Code that accesses the shared resource
    }
    finally
    {
        mutex.ReleaseMutex(); // Release the mutex
    }
    
    In this example, a mutex is used to ensure exclusive access to a shared resource by acquiring and releasing the mutex using the WaitOne and ReleaseMutex methods, respectively.

    Comments

    Popular posts from this blog

    Implementing and Integrating RabbitMQ in .NET Core Application: Shopping Cart and Order API

    RabbitMQ is a robust message broker that enables communication between services in a decoupled, reliable manner. In this guide, we’ll implement RabbitMQ in a .NET Core application to connect two microservices: Shopping Cart API (Producer) and Order API (Consumer). 1. Prerequisites Install RabbitMQ locally or on a server. Default Management UI: http://localhost:15672 Default Credentials: guest/guest Install the RabbitMQ.Client package for .NET: dotnet add package RabbitMQ.Client 2. Architecture Overview Shopping Cart API (Producer): Sends a message when a user places an order. RabbitMQ : Acts as the broker to hold the message. Order API (Consumer): Receives the message and processes the order. 3. RabbitMQ Producer: Shopping Cart API Step 1: Install RabbitMQ.Client Ensure the RabbitMQ client library is installed: dotnet add package RabbitMQ.Client Step 2: Create the Producer Service Add a RabbitMQProducer class to send messages. RabbitMQProducer.cs : using RabbitMQ.Client; usin...

    .NET 10: Your Ultimate Guide to the Coolest New Features (with Real-World Goodies!)

     Hey .NET warriors! 🤓 Are you ready to explore the latest and greatest features that .NET 10 and C# 14 bring to the table? Whether you're a seasoned developer or just starting out, this guide will show you how .NET 10 makes your apps faster, safer, and more productive — with real-world examples to boot! So grab your coffee ☕️ and let’s dive into the awesome . 💪 1️⃣ JIT Compiler Superpowers — Lightning-Fast Apps .NET 10 is all about speed . The Just-In-Time (JIT) compiler has been turbocharged with: Stack Allocation for Small Arrays 🗂️ Think fewer heap allocations, less garbage collection, and blazing-fast performance . Better Code Layout 🔥 Hot code paths are now smarter, meaning faster method calls and fewer CPU cache misses. 💡 Why you care: Your APIs, desktop apps, and services now respond quicker — giving users a snappy experience . 2️⃣ Say Hello to C# 14 — More Power in Your Syntax .NET 10 ships with C# 14 , and it’s packed with developer goodies: Field-Bac...

    Optional Parameters in C# — Writing Flexible and Clean Methods

    Hello, .NET developers! 👋 How often have you created multiple method overloads just to handle slightly different cases? Maybe one method accepts two parameters, another three, and one more adds a flag for debugging? That’s a lot of code duplication for something that can be solved beautifully with optional parameters . Optional parameters in C# let you define default values for method arguments. When a caller doesn’t pass a value, the compiler automatically substitutes the default. This feature helps keep your APIs simple, readable, and maintainable. 🎥 Explore more on YouTube : DotNet Full Stack Dev Understanding Optional Parameters Optional parameters are defined by assigning default values in the method signature. When calling the method, you can omit those parameters if you’re okay with the defaults. Example public class Logger { public void Log(string message, string level = "INFO", bool writeToFile = false) ...