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...

    Clean Architecture: What It Is and How It Differs from Microservices

    In the tech world, buzzwords like   Clean Architecture   and   Microservices   often dominate discussions about building scalable, maintainable applications. But what exactly is Clean Architecture? How does it compare to Microservices? And most importantly, is it more efficient? Let’s break it all down, from understanding the core principles of Clean Architecture to comparing it with Microservices. By the end of this blog, you’ll know when to use each and why Clean Architecture might just be the silent hero your projects need. What is Clean Architecture? Clean Architecture  is a design paradigm introduced by Robert C. Martin (Uncle Bob) in his book  Clean Architecture: A Craftsman’s Guide to Software Structure and Design . It’s an evolution of layered architecture, focusing on organizing code in a way that makes it  flexible ,  testable , and  easy to maintain . Core Principles of Clean Architecture Dependency Inversion : High-level modules s...

    How Does My .NET Core Application Build Once and Run Everywhere?

    One of the most powerful features of .NET Core is its cross-platform nature. Unlike the traditional .NET Framework, which was limited to Windows, .NET Core allows you to build your application once and run it on Windows , Linux , or macOS . This makes it an excellent choice for modern, scalable, and portable applications. In this blog, we’ll explore how .NET Core achieves this, the underlying architecture, and how you can leverage it to make your applications truly cross-platform. Key Features of .NET Core for Cross-Platform Development Platform Independence : .NET Core Runtime is available for multiple platforms (Windows, Linux, macOS). Applications can run seamlessly without platform-specific adjustments. Build Once, Run Anywhere : Compile your code once and deploy it on any OS with minimal effort. Self-Contained Deployment : .NET Core apps can include the runtime in the deployment package, making them independent of the host system's installed runtime. Standardized Libraries ...