Book Image

Customizing ASP.NET Core 6.0 - Second Edition

By : Jürgen Gutsch
Book Image

Customizing ASP.NET Core 6.0 - Second Edition

By: Jürgen Gutsch

Overview of this book

ASP.NET Core is packed full of hidden features for building sophisticated web applications – but if you don’t know how to customize it, you’re not making the most of its capabilities. Customizing ASP.NET Core 6.0 is a book that will teach you all about tweaking the knobs at various layers and take experienced programmers’ skills to a new level. This updated second edition covers the latest features and changes in the .NET 6 LTS version, along with new insights and customization techniques for important topics such as authentication and authorization. You’ll also learn how to work with caches and change the default behavior of ASP.NET Core apps. This book will show you the essential concepts relating to tweaking the framework, such as configuration, dependency injection, routing, action filters, and more. As you progress, you'll be able to create custom solutions that meet the needs of your use case with ASP.NET Core. Later chapters will cover expert techniques and best practices for using the framework for your app development needs, from UI design to hosting. Finally, you'll focus on the new endpoint routing in ASP.NET Core to build custom endpoints and add third-party endpoints to your web apps for processing requests faster. By the end of this book, you'll be able to customize ASP.NET Core to develop better, more robust apps.
Table of Contents (18 chapters)

Why do we need caching?

Caching speeds up performance, by storing the results in memory or in a distributed cache like a fast Redis database, you can also store cached data in files if it makes sense.

A distributed cache is needed in case you run multiple instances of an application to scale for availability of your application. The instances will run on multiple Docker containers, in a Kubernetes cluster or just on more than one Azure App Services. In that case, the instances should share a cache.

Most application caches are in-memory caches that store data for a short period of time. This is good for most scenarios.

Also, browser do cache the websites or the web applications output. The browsers usually store the entire result in files. As an ASP.NET developer you can control the browsers cache by adding HTTP headers that specify whether the browser should cache or not and that specify how long the cached item should be valid.

A browser cache reduces the number of requests...