Say we need to get the results for the third page of our website, counting 20 as the number of results we want. Ok, the easiest way to explain this is by example. Skip((ownerParameters.PageNumber - 1) * ownerParameters.PageSize) Void UpdateOwner(Owner dbOwner, Owner owner) Īnd the logic: public IEnumerable GetOwners(OwnerParameters ownerParameters) OwnerExtended GetOwnerWithDetails(Guid ownerId) IEnumerable GetOwners(OwnerParameters ownerParameters) Learning Web API? Get our eBook ASP.NET Core Web API Best Practices and become an expert for FREE! > GET THE BOOK Now, let’s implement the most important part, the repository logic. If not set by the caller, PageNumber will be set to 1, and PageSize to 10. We have two public properties – PageNumber and PageSize. We are using constant maxPageSize to restrict our API to a maximum of 50 owners. Learning Web API? Get our eBook ASP.NET Core Web API Best Practices and become an expert for FREE! > GET THE BOOK maxPageSize) ? maxPageSize : value So, having that in mind, let’s modify this method to support paging. Other scenarios are far less benign for your application and machines (imagine hosting it in the cloud and not having proper caching in place). The best-case scenario would be that you started out with a small number of owners that increased slowly over time so you can notice the slow decline in performance. We would end up with a very long query that returns A LOT of data. End then add to that, a few thousand of API consumers. What if there were thousands or even millions of people in the database (you wish, but still, imagine another kind of entity).

public IQueryable FindAll()Īs you can see it’s a straightforward action, meant to return all the owners from the database ordered by name.īut, in our case, that’s just a few account owners (five).

CacheProfileName: can point to cache profile setup in MVC middleware (see below).Learning Web API? Get our eBook ASP.NET Core Web API Best Practices and become an expert for FREE! > GET THE BOOK GetOwners()įindAll() method is just a method from a Base Repository class that return the whole set of owners.

VaryByHeader: used to set Vary HTTP response header.

VaryByQueryKeys: responses are cached based on query string parameters.

Location: translates into Cache-Control header of public, private or no-cache.

Duration: used to set cache expiry (in seconds).

The attribute has some useful parameters to alter the behaviour of the middleware. Once middleware is set up, attribute is applied to the controller/action to enable caching. It adds cache related headers to HTTP responses, primary one being Cache-Control. The Response Caching middleware is responsible for storing and serving the responses from a cache. The response will contain a Cache-Control header.Īs you navigate between a Controller with caching enabled (Home) and another one without it (Movies), you’ll notice that the time hasn’t been updated, i.e., it's not coming from the server but rather from the cache.

public class HomeController : Controller.

Asp.net core private cache