Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Pragmatic Microservices with C# and Azure
  • Table Of Contents Toc
  • Feedback & Rating feedback
Pragmatic Microservices with C# and Azure

Pragmatic Microservices with C# and Azure

By : Nagel
4.2 (11)
close
close
Pragmatic Microservices with C# and Azure

Pragmatic Microservices with C# and Azure

4.2 (11)
By: Nagel

Overview of this book

Pragmatic Microservices with C# and Azure introduces .NET Aspire for microservices, focusing on defining an app model, utilizing service discovery, and integrating with Azure's native cloud services. Written by a Microsoft MVP and seasoned software architect with over two decades of experience in .NET, this book will help you get to grips with robust service development using .NET features like minimal APIs, gRPC, and SignalR for real-time communication. Aside from covering essential aspects of DevOps, including testing methodologies such as unit, integration, and load testing, you’ll also explore logging and monitoring including OpenTelemetry using tools like Azure Log Analytics, Application Insights, Prometheus, and Grafana. You'll learn about asynchronous communication leveraging queues and events through Azure Event Hub and Apache. Throughout the book, theoretical aspects will be complemented by practical skills gained from building and deploying a fully functional microservices-based application. By the end, you’ll possess a deep understanding of microservices architecture, hands-on experience with various .NET technologies and Azure services, and the ability to design, build, deploy, and manage microservices applications effectively in both on-premises and cloud environments.
Table of Contents (23 chapters)
close
close
Free Chapter
1
Part 1: Creating Microservices with .NET
6
Part 2: Hosting and Deploying
12
Part 3: Troubleshooting and Scaling
16
Part 4: More communication options

Adding log messages

To see what’s going on successfully or not when running the solution, we add log messages. The important parts of understanding the concept of logging are the following:

  • The source: Who writes log information – what is the category name?
  • The log provider: Where is log information written to?
  • The log level: What is the level of the log message? Is it just information or an error?
  • Filtering: What information is logged?

The source is defined using the ILogger<T> generic interface. With this generic interface, the category name is taken from the class name of the generic parameter type. In case you use the ILoggerFactory interface instead of ILogger<T>, the category name is passed by invoking the CreateLogger method. Examples of category names used by .NET are Microsoft.EntityFrameworkCore.Database.Command, System.Net.Http.HttpClient, and Microsoft.Hosting.Lifetime. Having hierarchical names helps with common configuration...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY