Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Architecting ASP.NET Core Applications - Third Edition

You're reading from  Architecting ASP.NET Core Applications - Third Edition

Product type Book
Published in Mar 2024
Publisher Packt
ISBN-13 9781805123385
Pages 806 pages
Edition 3rd Edition
Languages
Author (1):
Carl-Hugo Marcotte Carl-Hugo Marcotte
Profile icon Carl-Hugo Marcotte
Toc

Table of Contents (27) Chapters close

Preface 1. Section 1: Principles and Methodologies
2. Introduction 3. Automated Testing 4. Architectural Principles 5. REST APIs 6. Section 2: Designing with ASP.NET Core
7. Minimal APIs 8. Model-View-Controller 9. Strategy, Abstract Factory, and Singleton Design Patterns 10. Dependency Injection 11. Application Configuration and the Options Pattern 12. Logging Patterns 13. Section 3: Component Patterns
14. Structural Patterns 15. Behavioral Patterns 16. Operation Result Pattern 17. Section 4: Application Patterns 18. Layering and Clean Architecture 19. Object Mappers 20. Mediator and CQS Patterns 21. Getting Started with Vertical Slice Architecture 22. Request-EndPoint-Response (REPR) 23. Introduction to Microservices Architecture 24. Modular Monolith 25. Other Books You May Enjoy
26. Index

What is logging?

Logging is the practice of writing messages into a log and cataloging information for later use. Logging is a cross-cutting concern, meaning it applies to every piece of your application. We talk about layers in Chapter 14, Layering and Clean Architecture, but until then, let’s just say that a cross-cutting concern affects all layers and cannot be centralized in just one; it affects a bit of everything.

Logging is essential for several reasons, including:

  • Error diagnosis: Logging helps capture runtime errors and stack traces, which are invaluable for diagnosing issues after they occur, especially once an application is in production
  • Debugging support: Detailed logs can provide context when debugging, helping developers understand the application’s state at the time of an error or exception
  • Performance monitoring: By logging performance metrics, you can identify bottlenecks and optimize the efficiency of your application
  • ...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime