This is yet another post in a series
on creating performant and scalable web APIs using ASP.NET Core. In this post, we'll start to focus on caching. Often the slowest bit of a web API is fetching the data, so, if the data hasn't changed it makes sense to save it in a place that can be retrieved a lot quicker than a database or another API call.
We will focus on leveraging standard HTTP caching and in this post we'll focus on client side caching. There are 2 HTTP caching approaches: - expiration