Book Image

C# 7 and .NET Core 2.0 High Performance

By : Ovais Mehboob Ahmed Khan
Book Image

C# 7 and .NET Core 2.0 High Performance

By: Ovais Mehboob Ahmed Khan

Overview of this book

While writing an application, performance is paramount. Performance tuning for realworld applications often involves activities geared toward fnding bottlenecks; however, this cannot solve the dreaded problem of slower code. If you want to improve the speed of your code and optimize an application's performance, then this book is for you. C# 7 and .NET Core 2.0 High Performance begins with an introduction to the new features of what?explaining how they help in improving an application's performance. Learn to identify the bottlenecks in writing programs and highlight common performance pitfalls, and learn strategies to detect and resolve these issues early. You will explore multithreading and asynchronous programming with .NET Core and learn the importance and effcient use of data structures. This is followed with memory management techniques and design guidelines to increase an application’s performance. Gradually, the book will show you the importance of microservices architecture for building highly performant applications and implementing resiliency and security in .NET Core. After reading this book, you will learn how to structure and build scalable, optimized, and robust applications in C#7 and .NET.
Table of Contents (11 chapters)
Designing Guidelines for .NET Core Application Performance

Coding principles

In this section, we will cover some of the basic coding principles that help in writing quality code that improves the overall performance and scalability of the application.

Naming convention

Always use the proper naming convention in every application, starting with the solution name, which should provide meaningful information about the project you are working on. The project name specifies the layer or component part of the application. Finally, classes should be nouns or noun phrases, and methods should represent the actions.

When we create a new project in Visual Studio, the default solution name is set to what you specify for the project name. The solution name should always be different from the project...