Book Image

Hands-On Parallel Programming with C# 8 and .NET Core 3

By : Shakti Tanwar
Book Image

Hands-On Parallel Programming with C# 8 and .NET Core 3

By: Shakti Tanwar

Overview of this book

In today’s world, every CPU has a multi-core processor. However, unless your application has implemented parallel programming, it will fail to utilize the hardware’s full processing capacity. This book will show you how to write modern software on the optimized and high-performing .NET Core 3 framework using C# 8. Hands-On Parallel Programming with C# 8 and .NET Core 3 covers how to build multithreaded, concurrent, and optimized applications that harness the power of multi-core processors. Once you’ve understood the fundamentals of threading and concurrency, you’ll gain insights into the data structure in .NET Core that supports parallelism. The book will then help you perform asynchronous programming in C# and diagnose and debug parallel code effectively. You’ll also get to grips with the new Kestrel server and understand the difference between the IIS and Kestrel operating models. Finally, you’ll learn best practices such as test-driven development, and run unit tests on your parallel code. By the end of the book, you’ll have developed a deep understanding of the core concepts of concurrency and asynchrony to create responsive applications that are not CPU-intensive.
Table of Contents (22 chapters)
Free Chapter
1
Section 1: Fundamentals of Threading, Multitasking, and Asynchrony
6
Section 2: Data Structures that Support Parallelism in .NET Core
10
Section 3: Asynchronous Programming Using C#
13
Section 4: Debugging, Diagnostics, and Unit Testing for Async Code
16
Section 5: Parallel Programming Feature Additions to .NET Core

Introducing lazy initialization concepts

Lazy loading is a commonly used design pattern in application programming wherein we defer the creation of an object until it is actually required in an application. Proper use of the lazy load pattern can significantly improve the performance of the application.

One of the common usages of this pattern can be seen in cache aside patterns. We use the cache aside pattern for objects whose creation is expensive either in terms of resources or memory. Instead of creating them multiple times, we create objects once and cache them for future use. This pattern is possible when the initialization of an object is moved out of the constructor to the method or properties. The object will only be initialized when the method or property is called for the first time by code. It will then be cached for subsequent calls. Take a look at the following code...