The NEW caching you should be using in .NET 7

Hello everybody I'm Nick and in this video I will introduce you to the brand new output caching feature that is added in .NET 7. It fixes a lot of the issues with the existing response caching feature and I'm absolutely in love with its simplicity, extensibility and API.

Workshops

Don't forget to comment, like and subscribe :)

Social Media:

#csharp #dotnet #caching

[ExpensivePizza]

There are 2 hard problems in computer science: cache invalidation, naming things and off-by-1 errors.

[Szwarcus]

Like learning from your videos. "Alexis Texas" made my day 🤣🤣

[Dustyy]

Just an amazing showcase in this short video. Very very helpful for many ppl🔥👍

[OldShoolGames]

Great video as always, thank you for your effort !

[sinoergin]

Great video dude. Also new caching system is look like powerful. Thanks for ur effort!

[greenwoodricky]

Absolute legend. Just implemented caching and needed to evict by id and I was struggling to find anything anywhere.

[charliesta.abc]

The web is about to get a massive performance boost !

This is awesome

[maciejgawe]

Best .NET channel mate, short but full of info

[antonmartyniuk]

Fantastic feature. Will use it day 1 after release of .NET 7

[sadaja]

Hi Nick, super awsome content, as usual :)

[EwanDobsonFan]

Very nice feature can’t wait to try this out

[alexclark]

Not sure if there's a way around this when defining policies, but it would be nice if there was a "non-blocking" solution to when the cache has an expired entry that's being requested by the client. I wrote a simple cache mechanism a while back which would return the "stale" object to the client while updating the cache in the background when it determined (triggered by a request) that the entry had outlived its expiration date. The vast majority of the time the client didn't care that it was getting something that was (for e.g.) 61 minutes old, especially if it meant a rapid response. Often times throughput is more important than rigidly adhering to the policy's TTL.

[EdKolis]

This looks really useful! Thanks for explaining it, it's not all that intuitive looking!

[StuartHemming]

Would love to see how this new stuff works in conjunction with Redis

[Kingside]

Caching is great and I like the new feature.
Also your'e presantation was great.
But as always with caching: When the application grows and data became complex caching can open hard to maintain issues

[avunda]

Hey Nick, and thank you for all amazing content! Any plans on making a video on structs? When to use them, what pitfalls to avoid etc.

[juanmiguel]

Is it better having the IDs as guid or is it perfectly fine having them as integers ?

[catalan]

Hey Nick thanks so much for the awesome content! Could you tell which font you're using?

[windfisch]

Is it also possible to use this cache in gRPC services?

[stanislav]

Hey Nick, thank you for the video!
I have a small question about your example.
In the POST handler, the service creates the customer, evicts the cache by tag, and you pass the cancellation token there (11:10).
But what if the user cancels the request before the EvictByTagAsync method invokes, will it lead to the behavior when the customer was created but the cache is not evicted?

Thank you very much!