You're reading from Enterprise Application Development with C# 9 and .NET 5 Enhance your C# and .NET skills by mastering the process of developing professional-grade web applications

Product type Paperback

Published in Mar 2021

Publisher Packt

ISBN-13 9781800209442

Length 610 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Application Development

Authors (5):

Ravindra Akella

Suneel Kumar Kunani

Bhupesh Guptha Muthiyalu

Arun Kumar Tamirisa

Rishabh Verma

+1 more

View More author details

Table of Contents (24) Chapters

Preface

1. Section 1: Architecting an Enterprise Application and its Fundamentals

2. Chapter 1: Designing and Architecting the Enterprise Application FREE CHAPTER

3. Chapter 2: Introducing .NET 5 Core and Standard

4. Chapter 3: Introducing C# 9

5. Section 2: Cross-Cutting Concerns

6. Chapter 4: Threading and Asynchronous Operations

7. Chapter 5: Dependency Injection in .NET

8. Chapter 6: Configuration in .NET Core

9. Chapter 7: Logging in .NET 5

10. Chapter 8: Understanding Caching

11. Section 3: Developing Your Enterprise Application

12. Chapter 9: Working with Data in .NET 5

13. Chapter 10: Creating an ASP.NET Core 5 Web API

14. Chapter 11: Creating an ASP.NET Core 5 Web Application

15. Section 4: Security

16. Chapter 12: Understanding Authentication

17. Chapter 13: Understanding Authorization

18. Section 5: Health Checks, Unit Testing, Deployment, and Diagnostics

19. Chapter 14: Health and Diagnostics

20. Chapter 15: Testing

21. Chapter 16: Deploying the Applications in Azure

22. Assessments

23. Other Books You May Enjoy

Characteristics of good logging

How many times you have seen this issue? Logging is implemented but the information in the logs is not useful for building insights or debugging production issues. That's where best practices come into the picture, to implement good logging in your application. Some of the characteristics of good logging are as follows:

It should not affect the actual application performance.
It should be accurate and complete.
It should be leveraged for data analytics and learning about application usage, such as concurrent users, peak load time, most/least used features, and so on.
It should help us reproduce the issue reported for root cause analysis and minimize "unable to reproduce" instances.
It should be distributed and easily accessible by everyone – development, product owner, and support.
It should not contain protected or sensitive info, personally identifiable information (PII), or duplicate or unnecessary...