I always thought that caching was a mess to integrate. After seeing your video, it took literally 5 minutes to make it work. Thanks a lot mate, you're amazing!
I am glad it was helpful. Caching itself is actually fairly easy. The difficulty will come in when it comes to deciding when to invalidate the cache and get fresh data.
Hi Tim, first I have to say thank you so much for everything you did and are doing for me and for literally thousands of developers around the world! I have one very small critique. I'm not a native English speaker, and sometimes I feel like a word you say every few sentences gets lost on me, almost as if you're saying the word in shorthand form, perhaps because you're very used to the language. Once again thank you very much Tim, you are a true teacher.
22:05 "one of those 'Tim's Gonna Make Sure You're Clear On This' section" Haha! 😁Love it. Thank you Tim for the clarity and depth. Your efforts are more than commendable in this field! 👍
Very interesting. Usually backend is stateless. This is a way, better way to make it to manage also state, without using static statement that is dangerous in web applications
Awesome! Thanks a lot, Tim for the detailed tutorial. To me, your tutorials are unique because you explain How to use When it should be used When it should not be used and also mention the alternative tool/approach. Today I learned about In-Memory Cache and Redis.
Hello Tim. You are a great teacher. I am learning a lot from your courses. Do you have any plan for a DEMO on how to implement SSO in Net Core Web apps? Thank you.
This saves alot of dev time now that I don't have to run a redis container every time. (but ofcourse still stick to redis when it comes to heavy caching)
15:30 if you say this is shared across instances...do you mean this is shared between multiples instances of your web application? So if there are 2 instances running to distribute workload, does every instance have it's own cache of employees or do they access all the same? And is this threadsafe?
Nice caching overview. Can you also talk about the best ways to support apps that have a large amount of data? I think caching is definitely a peice of it, but I would like to migrate a data-heavy winforms/wpf app to blazor and I would like to see how you would go about managing a large set of data (large being 1gb+) and if blazor can even handle data like that without extreme amounts of paging ect...
When we build desktop apps, we tend to get a bit lazy with our data because we have such power available to us on the client side. If you think about 1GB of data, and how much content that represents, you will see that it is too much to display to the user. Yes, you might "need" all of that data but the user never sees that much. If we converted 1GB into 200-page books, we would need over 4,000 of them. So when you move to the web (or honestly even before since the same principle is true on the desktop - the web just forces you to work differently), you need to think about what is actually needed. For instance, if you have a list of employees, you probably just need a few pieces of information (name, Id, department, title), not all of the information about an employee. So, you create a query that gets you just that information. Then, you don't need to display all of the employees for your entire organization on the screen at once (even hidden behind a scroll). Load just the records they need to see. That might require you to do multiple queries if they want to scroll manually through the list. You can use the Virtualize panel in Blazor to help make that more transparent. You will have to do some work, but that work should be done in both apps, not just the web app.
@@IAmTimCorey I see this almost obsessive trait, of wanting to move from desktop to a web environment and it is just crazy to me. In the end, it has little thought for the end user and thinks only about the developer. The user experience will be objectively and measurably worse in a web application, there is no denying this, you even hint at that yourself, one of the many, many reasons. Don't move to web because some manager who does not care the slightest about the end user experience wants to use web-devy stuff. Think about the end user and the problem you are trying to solve, instead.
I use a lot of in memory caching in an older version of .Net. It is very similar to what you are doing here but I do one thing I didn't notice in the video, I clear the cache manually in some circumstances. Adds, Edits, and Deletes of record lists that I have cached for instance. Can you set the value of the cache to null to clear it manually or are you constrained to the expiration datetime?
Yes, you can clear the values. Just use the Remove method: docs.microsoft.com/en-us/dotnet/api/system.runtime.caching.memorycache.remove?view=dotnet-plat-ext-6.0
Which is the best way to cache image url to be downloaded once but displayed in different divs, i have been searching about image url caching in blazor web assemple but to where to find a good source of information. To display the images i am using I want to catch the image from this div to the use this images in order div without needing to use resorses to downoad the image again in the other divs withe same methodology of backgound-image url.
thanks man it is amazing but what about concurrent request for the same cache key if two request check the same key they will ask the database twice and set the key twice . is there any solution for that ?
Good question. It depends on if this is a problem. First, this probably won't happen often. However, if it does happen, the worst-case scenario is that you call the database twice instead of once and that you overwrite the cache with the second call to set the value. But if that is a serious problem, you could implement a service that does caching in order. Then it could deduplicate requests. I think that's a lot of extra overhead for every call when the problem it is solving has such a low impact.
@@IAmTimCorey I was also wondering about the thread-safety of memory cache... although, tbh, my main concern is about thread-safety of Redis cache, as I intend to use memory cache only in dev environment, and Redis in production.
Hi Tim, Thanks - I learn something new today. Not in deep, but enough to understand where to look if needed. One side question, indirectly related with caching. Given relatively big document. Memory is enough to keep it in memory. Document are consumed by several threads. Read-only mode. And here came a problem: - can't have a copy of the document for each thread - too much memory require; - can't use pipes for to interact between main storage and thread - too slow; Need some kind of common memory shared between threads, but threads are isolated. Any sods about how to approach this problem will be appreciated.
Good one, thanks! But what is the difference between mem cache and storing the result in a property and refreshing that after x minutes via for instance a Hangfire job? And don't say You won't need Hangfire anymore :) Asking because I want to use some sort of caching in my portfolio app.
Hi, Tim! As always, great and useful explanation! Sometimes I face the cases, when there is no any predefined timespan for cache to live, but you want the data, which got changed in the database, to be immediately become up-to-date. Is there a way to achieve that? Like, when the data in DB table is changed, some kind of trigger is burned and the data in in-memory cache (or, whatever else) becomes synced to the data in the table.
Thank you Tim, Great Video, btw can you tell me how can i add that extension which indicates parameter types in Methods .Delay(millisecondsDelay: 3000)
Hi Tim, Great tutorial! Do you have any tutorials on automatically repopulating your IMemoryCache from the database after a few hours? I don't have many queries but they are large and the db loads gets new data once a day. I cant quite figure out how its done from stack overflow.
HELLO..did you watch the video? he showed it. In method you calling cached data, you should populate it if cache is expired/null. So just read data and put it in cache. so you got auto repupulation. If you want auto populate cache even if nobody ask for data - then your idea is dumb and you should not develop apps, because it's dumb to keep data in memory if nobody even asks for it.
@@SayWhaaaaaaaaaaaaaaaaaaaaaaat Hi Tomas, I did watch the video but I would like to repopulate the data after it expires automatically. My ASP Core app has queries that need 15+ seconds and I cant ask the user to deal with that or do it myself each morning. I have seen examples with PostEvicitionCallbacks and ExpirationTokens that should solve the need but I am having trouble.
Hey Tim!, Thank you very much. It's a nice video. I have one quick question. Does the cache affect the worker process memory usage or it is something out of process memory management?
Hey Tim, great topic. But what about racing conditions? Shouldn't you recheck with a TryGet just before you tried to set the entry if another thread has set it already on the meantime? Assuming that double-setting of (different) data would be problematic.
Worst case, you double-set it. Not a big deal, since if you didn't have caching then you would be getting that data every time. If your data would change based upon the new call then you shouldn't be caching the data.
It is in the memory of the computer running the application. So for most web projects, that means the server. The exception would be for Blazor WebAssembly projects, where it would be in the client's memory.
Hello Tim, Very informative and clean explanation. Thanks.. What if any user adds a new Employee to database? Shall we remove and create the new cache or is there a way to edit the cache?
Typically forms are on the client-side and this caching is server-side, so you would need to look at a client-side cache like SessionStorage or LocalStorage unless you wanted to post a partial form to the server.
Hi. Thanks for the tutorial. One question. When handling with large data and many users. A thread problem can happens? Meaning 2 threads think the orders are null?
Yes, between the time you check for records and when you set the records in the cache, someone else can do the same thing. That would result in multiple people doing the data lookup from the database. That's not a huge deal in most cases. If it is, you can use LazyCache to wrap this so that you only get one database read.
Hi Tim, Assuming the same request happens in a short amount of time, lets say the cache is empty at this point. Now lets say request A is called to get employees and it takes 10 seconds. but before 10 seconds pass, after about 6 seconds, another request was made - ie: request B Now since request A and request B should return the same thing, there is no point in processing both. So i want request A to process, and have request B wait for the result to be populated in the cache then return the cached result. How would you go about implementing something like this?
That would be a lot of work for little return. You could create a class with a completion event and an indicator when the class has been activated. Then, the first call activates the class and subscribes to the completed event. Every subsequent call could subscribe to the event only, knowing the call is in progress. However, that's a lot of additional overhead when it usually isn't necessary. Caching isn't about never making a duplicate call. It is about reducing the number of calls. You should be able to function without caching. In the case of your 10-second call, the first thing I would do is work on reducing that number. 10 seconds is a LONG time to wait for something. If you could add some complexity to reduce that call to 3 second, the number of duplicate calls you would have would go down and the overall experience for everyone would be better. Another option for long-running calls like that is to only let the system kick them off. Always work from the cache and have the system handle refreshing it in the background. That way, you never have duplicate calls, and the initial call happens on system load, so no one is ever waiting those 10 seconds.
If you have a website and your using memory cache, does it cache the memory on the person using the websites computer or does it cache it on the servers memory?
Time isn't really the issue here, it is the content. So what content are you hoping to cut? These videos are about preparing you to use a topic in the real world, not just a "here is what this topic is"-type. I do have the 10-minute training series for those types of videos.
Store the data the user will actually need. For instance, do they actually need a million records? If so, caching probably needs to happen on Redis or something similar. Another test is what are they coming back to repeatedly?
What if you know the data is not going to change? Is there any reason in such cases to use the cashing rather than just load it in a singleton service?
What if I have an event that tells me that an employee has been added, changed or deleted so I can expire the cache Instead of giving a short time and the data is still not changed is it a good practice?
May I ask you what is difference if I create a Singleton repository and load all data into some private field inside the class? can I imitate In Memory Caching using this approach? because every hour first I check the data Count first if there are something added to my data then I will reload my repository again
> because every hour ... I will reload You can write... but do you need to write something? All already written and need just set 1 hour timeout. > if there are something added You can update your cache any time you want. It just hashtable in the memory - use the same key and replace the object.
@@AMurr-zm4wh if we set the Memory Expiry to 1 hour then after 1 hour we need to reload again (IO cost) but if I check just count of records every hour maybe I don't need to reload again for a couple of hours and it means less IO cost (I need to add new records to my pool only)
@@nadervaghari51 Ok. Set 2 hour timeout and update cache in 1 hour. Take object out of the cache, add if you have something to add to the object and put it back into cache - this will reset the timer. In this way you not need to write any additional code.
@@nadervaghari51 Yes, you can. At least I use it in the past in global.asax - there was no other way at time. But main question is different - Why do you want to write and support additional code in place where nothing need to be written?
The title is slightly misleading. This is not C# in general, it is a specific use case stuck in the web mindset. Can you show us how this applies, for example, to WPF or maybe even Xamarin?
The way how your explain caching here is much better than in your paid course webapi about caching, like here you even expain with blazor just like in real world so much better but WHY? @IamTimCorey. I Thought paid course could me litle bit more like this?
The course isn't about in-memory caching. The course is about the API project template. We cover a LOT of ground in that course, but we don't go into depth on things beyond the scope of the course. So yes, you will find more in-depth topics on this channel or in other courses that are more specific to the topic you are looking into. The API course goes into depth on API, not on all of the connected items. Otherwise, it would be a MASSIVE course. Also, the primary purpose of a course is to lead you down the path of learning a technology in a structured, ordered manner. That is the main benefit of the course. There will always be more depth to go into, more things to learn, and more areas to grow in after you gain the foundational knowledge of the topic.
I like these short videos with simple and complete examples.
Thanks!
Best tutorial I have found for caching. Great work Tim and keep the videos coming.
Thanks!
I always thought that caching was a mess to integrate. After seeing your video, it took literally 5 minutes to make it work.
Thanks a lot mate, you're amazing!
I am glad it was helpful. Caching itself is actually fairly easy. The difficulty will come in when it comes to deciding when to invalidate the cache and get fresh data.
@@IAmTimCorey Exactly. Some people suggest to Dispose and create a new fresh instance.. but I don't think it's a valid solution.
Hi Tim, first I have to say thank you so much for everything you did and are doing for me and for literally thousands of developers around the world!
I have one very small critique. I'm not a native English speaker, and sometimes I feel like a word you say every few sentences gets lost on me, almost as if you're saying the word in shorthand form, perhaps because you're very used to the language.
Once again thank you very much Tim, you are a true teacher.
I am glad you are finding my content valuable. Thanks for the note. I will try to pay attention to that.
22:05 "one of those 'Tim's Gonna Make Sure You're Clear On This' section" Haha! 😁Love it.
Thank you Tim for the clarity and depth. Your efforts are more than commendable in this field! 👍
You are most welcome.
You didn't lie when you responded to my comment just the other day telling me that you would do a video on this soon!! Your the man!
Yep, it was already in progress.
Very interesting. Usually backend is stateless. This is a way, better way to make it to manage also state, without using static statement that is dangerous in web applications
Thanks for lesson.
I like that you speak so clearly. So i can understand all the things
Glad to hear that!
oh Tim you're awesome! I can't stop watching your tutorials, I 'm gonna cancel my Netflix subscription! 👌😊
I am glad you are enjoying them.
Awesome! Thanks a lot, Tim for the detailed tutorial. To me, your tutorials are unique because you explain
How to use
When it should be used
When it should not be used
and also mention the alternative tool/approach.
Today I learned about In-Memory Cache and Redis.
You are welcome.
At the right time! I was just looking at some literature on this subject. Thanks Tim! 👍🏽
You are welcome.
That was shockingly easy to implement. Thanks as always. Keep up the great work.
You are welcome.
Thank you very much Tim for every thing you are sharing with us , Keep up PLEASE
You are welcome.
Most definately something I could see myself using in one of my projects I have.
Excellent!
As always, good stuff. Thanks Tim
You are welcome.
I wasn't aware of the Microsoft caching extension. Thank you and good advice.
You are welcome.
Thank you Tim Corey 😊🙏🏻
This video was very good 👍🏻
You are most welcome. Thanks for watching.
thank you very much for this excellent and clear intro
You are welcome.
1:56 ... I have no idea what was said there, but all I heard was 'we're gonna start ripping ass right away' and now I can't unhear it 🤣🤣🤣
Hi, Tim! It was an excellent explanation; thank you so much!
You're very welcome!
Audio sounds a bit wonkey. Can't put my finger on what it is, though. What you say is still understandable, so it is not a major issue.
Yeah, I'm trying to figure out what the issue is.
@@IAmTimCorey Sounds almost like a directional mic that was pointed the wrong way. Picks up your voice indirectly so it is missing a lot of signal.
I am officially calling you psychic I was just thinking of how to do it and here you go a video of how to do it 😂😂😂.
I'm glad it came in time.
Yet another awesome tutorial from Tim . ; ]
Thanks!
Thanks TIm , It's a Crystal clear.
You are welcome. I am glad it was helpful.
Thank you Tim for this wonderful video it was really very helpful.
You are welcome.
Great lesson, Tim! Thanks again.
You are welcome.
Nice video. Thanks for detail explanation.
You are welcome.
Hello Tim. You are a great teacher. I am learning a lot from your courses.
Do you have any plan for a DEMO on how to implement SSO in Net Core Web apps?
Thank you.
Not in the short term, but that is something I am considering.
This saves alot of dev time now that I don't have to run a redis container every time. (but ofcourse still stick to redis when it comes to heavy caching)
Yep, that's true.
15:30 if you say this is shared across instances...do you mean this is shared between multiples instances of your web application? So if there are 2 instances running to distribute workload, does every instance have it's own cache of employees or do they access all the same? And is this threadsafe?
Nevermind my first question :D Maybe I should watch the whole video^^ Thanks! Awesome video!
so helpful, Tim, thank you!!
You are welcome.
Very nice and good explanation..
Thank you!
Nice caching overview. Can you also talk about the best ways to support apps that have a large amount of data? I think caching is definitely a peice of it, but I would like to migrate a data-heavy winforms/wpf app to blazor and I would like to see how you would go about managing a large set of data (large being 1gb+) and if blazor can even handle data like that without extreme amounts of paging ect...
When we build desktop apps, we tend to get a bit lazy with our data because we have such power available to us on the client side. If you think about 1GB of data, and how much content that represents, you will see that it is too much to display to the user. Yes, you might "need" all of that data but the user never sees that much. If we converted 1GB into 200-page books, we would need over 4,000 of them. So when you move to the web (or honestly even before since the same principle is true on the desktop - the web just forces you to work differently), you need to think about what is actually needed. For instance, if you have a list of employees, you probably just need a few pieces of information (name, Id, department, title), not all of the information about an employee. So, you create a query that gets you just that information. Then, you don't need to display all of the employees for your entire organization on the screen at once (even hidden behind a scroll). Load just the records they need to see. That might require you to do multiple queries if they want to scroll manually through the list. You can use the Virtualize panel in Blazor to help make that more transparent. You will have to do some work, but that work should be done in both apps, not just the web app.
@@IAmTimCorey I see this almost obsessive trait, of wanting to move from desktop to a web environment and it is just crazy to me. In the end, it has little thought for the end user and thinks only about the developer. The user experience will be objectively and measurably worse in a web application, there is no denying this, you even hint at that yourself, one of the many, many reasons.
Don't move to web because some manager who does not care the slightest about the end user experience wants to use web-devy stuff. Think about the end user and the problem you are trying to solve, instead.
I use a lot of in memory caching in an older version of .Net. It is very similar to what you are doing here but I do one thing I didn't notice in the video, I clear the cache manually in some circumstances. Adds, Edits, and Deletes of record lists that I have cached for instance. Can you set the value of the cache to null to clear it manually or are you constrained to the expiration datetime?
Yes, you can clear the values. Just use the Remove method: docs.microsoft.com/en-us/dotnet/api/system.runtime.caching.memorycache.remove?view=dotnet-plat-ext-6.0
15:00 for Memory Caching
Hi Tim,
great Video.
Do you actually have a video about adding dependency injection into a desktop application?
Excellent Tutorial...
Thank you!
Why we are transient for DataAccess DI, if all of them would see the same data? Why not singleton too ?
Which is the best way to cache image url to be downloaded once but displayed in different divs, i have been searching about image url caching in blazor web assemple but to where to find a good source of information.
To display the images i am using
I want to catch the image from this div to the use this images in order div without needing to use resorses to downoad the image again in the other divs withe same methodology of backgound-image url.
thanks man it is amazing
but what about concurrent request for the same cache key
if two request check the same key they will ask the database twice and set the key twice .
is there any solution for that ?
locks? Can't think of anything else
Good question. It depends on if this is a problem. First, this probably won't happen often. However, if it does happen, the worst-case scenario is that you call the database twice instead of once and that you overwrite the cache with the second call to set the value. But if that is a serious problem, you could implement a service that does caching in order. Then it could deduplicate requests. I think that's a lot of extra overhead for every call when the problem it is solving has such a low impact.
@@IAmTimCorey I was also wondering about the thread-safety of memory cache... although, tbh, my main concern is about thread-safety of Redis cache, as I intend to use memory cache only in dev environment, and Redis in production.
Hi Tim,
Thanks - I learn something new today. Not in deep, but enough to understand where to look if needed.
One side question, indirectly related with caching.
Given relatively big document. Memory is enough to keep it in memory.
Document are consumed by several threads. Read-only mode.
And here came a problem:
- can't have a copy of the document for each thread - too much memory require;
- can't use pipes for to interact between main storage and thread - too slow;
Need some kind of common memory shared between threads, but threads are isolated.
Any sods about how to approach this problem will be appreciated.
Good one, thanks! But what is the difference between mem cache and storing the result in a property and refreshing that after x minutes via for instance a Hangfire job? And don't say You won't need Hangfire anymore :) Asking because I want to use some sort of caching in my portfolio app.
Wait, your new .NET 6 project already started with the usings without messing with the project file?
How do I do that?
Hi, Tim! As always, great and useful explanation! Sometimes I face the cases, when there is no any predefined timespan for cache to live, but you want the data, which got changed in the database, to be immediately become up-to-date. Is there a way to achieve that? Like, when the data in DB table is changed, some kind of trigger is burned and the data in in-memory cache (or, whatever else) becomes synced to the data in the table.
have you found out how to achieve that?)
Couldn't you use a singleton for the SampleDataAccess?
Hi Tim, Could you please make a video on threading in c sharp ,dotnet core
in detail
The top two results will cover almost all of your threading needs: ua-cam.com/users/IAmTimCoreysearch?query=async
@@IAmTimCorey thank you sir for response
Thank you Tim, Great Video, btw can you tell me how can i add that extension which indicates parameter types in Methods .Delay(millisecondsDelay: 3000)
Here you go: ua-cam.com/video/morBKqtqmso/v-deo.html
@@IAmTimCorey thank you again 🙏
Hi Tim, Great tutorial! Do you have any tutorials on automatically repopulating your IMemoryCache from the database after a few hours? I don't have many queries but they are large and the db loads gets new data once a day. I cant quite figure out how its done from stack overflow.
HELLO..did you watch the video? he showed it. In method you calling cached data, you should populate it if cache is expired/null. So just read data and put it in cache. so you got auto repupulation.
If you want auto populate cache even if nobody ask for data - then your idea is dumb and you should not develop apps, because it's dumb to keep data in memory if nobody even asks for it.
@@SayWhaaaaaaaaaaaaaaaaaaaaaaat Hi Tomas, I did watch the video but I would like to repopulate the data after it expires automatically. My ASP Core app has queries that need 15+ seconds and I cant ask the user to deal with that or do it myself each morning. I have seen examples with PostEvicitionCallbacks and ExpirationTokens that should solve the need but I am having trouble.
Hello tim,
Can you please help in extending this example with CRUD example? So how value get updates and available to all with caching?
Watch the Suggestion Site App course here on UA-cam. We will be using in-memory caching in the app.
@@IAmTimCorey
Ok got it. Thanks
Oh wow, how I missed ur tutorials. Thank you so much for this. A question: is memorycache thread safe?
Yes, it is thread safe.
Hey Tim!,
Thank you very much. It's a nice video. I have one quick question. Does the cache affect the worker process memory usage or it is something out of process memory management?
Hi Tim. I love watching your videos. Do you have any video talking about lazy loading ef database model set up ?
I don't. I don't really cover EF, except for one video.
Do you use another Mic? Quality was better before. Thanks for the vid.
Different room and I’m still working through the best setup.
Many Thanks, Tim !
You are welcome!
Hey Tim, great topic. But what about racing conditions? Shouldn't you recheck with a TryGet just before you tried to set the entry if another thread has set it already on the meantime? Assuming that double-setting of (different) data would be problematic.
Worst case, you double-set it. Not a big deal, since if you didn't have caching then you would be getting that data every time. If your data would change based upon the new call then you shouldn't be caching the data.
Hi ,
I am your huge fan.
However I have one silly question.
Is it in memory cache of server or the browser (client) ??
It is in the memory of the computer running the application. So for most web projects, that means the server. The exception would be for Blazor WebAssembly projects, where it would be in the client's memory.
Hello Tim, Very informative and clean explanation. Thanks.. What if any user adds a new Employee to database? Shall we remove and create the new cache or is there a way to edit the cache?
Typically the best option is to invalidate the cache and reload it.
Would this work for caching data for a loooooong form? Assign the fields to the output and then add to the memory
cache after X minutes?
Typically forms are on the client-side and this caching is server-side, so you would need to look at a client-side cache like SessionStorage or LocalStorage unless you wanted to post a partial form to the server.
Hi. Thanks for the tutorial.
One question. When handling with large data and many users. A thread problem can happens? Meaning 2 threads think the orders are null?
Yes, between the time you check for records and when you set the records in the cache, someone else can do the same thing. That would result in multiple people doing the data lookup from the database. That's not a huge deal in most cases. If it is, you can use LazyCache to wrap this so that you only get one database read.
Hi Tim,
Assuming the same request happens in a short amount of time,
lets say the cache is empty at this point.
Now lets say request A is called to get employees and it takes 10 seconds.
but before 10 seconds pass, after about 6 seconds, another request was made - ie: request B
Now since request A and request B should return the same thing, there is no point in processing both.
So i want request A to process, and have request B wait for the result to be populated in the cache then return the cached result.
How would you go about implementing something like this?
That would be a lot of work for little return. You could create a class with a completion event and an indicator when the class has been activated. Then, the first call activates the class and subscribes to the completed event. Every subsequent call could subscribe to the event only, knowing the call is in progress. However, that's a lot of additional overhead when it usually isn't necessary. Caching isn't about never making a duplicate call. It is about reducing the number of calls. You should be able to function without caching. In the case of your 10-second call, the first thing I would do is work on reducing that number. 10 seconds is a LONG time to wait for something. If you could add some complexity to reduce that call to 3 second, the number of duplicate calls you would have would go down and the overall experience for everyone would be better. Another option for long-running calls like that is to only let the system kick them off. Always work from the cache and have the system handle refreshing it in the background. That way, you never have duplicate calls, and the initial call happens on system load, so no one is ever waiting those 10 seconds.
Great Video, I have one doubt can we use combination of memory caching and also response caching at a time on the same action!
Yep. You will just need to manage your cache invalidation periods so you don't cause an issue.
Hi Tim,
Thanks a lot for the detailed info with examples.
Does the cache stored on RAM or on disk?
In RAM, although if the memory pressure on your web server, your web server might offload some to disk. However, that is a transparent process to you.
Using tryget would be the preferred way. Much cleaner too.
If you have a website and your using memory cache, does it cache the memory on the person using the websites computer or does it cache it on the servers memory?
On the server unless you are running Blazor WebAssembly, which runs on the client's machine.
If you could get videos under 20 minutes, that'd be so much better.
Thank you!
Time isn't really the issue here, it is the content. So what content are you hoping to cut? These videos are about preparing you to use a topic in the real world, not just a "here is what this topic is"-type. I do have the 10-minute training series for those types of videos.
Hi Tim, how to decide how much data I can store in memory. I'm I cannot just store millions of record.
Store the data the user will actually need. For instance, do they actually need a million records? If so, caching probably needs to happen on Redis or something similar. Another test is what are they coming back to repeatedly?
What if you know the data is not going to change? Is there any reason in such cases to use the cashing rather than just load it in a singleton service?
Memory pressure. If your memory pressure gets too high, you can flush the cache. That's not as easy with a singleton.
Thank you Tim.
You are welcome.
What are the advantages of using this over say the Azure Redis service?
In memory is quick and for small jobs. Redis is for when those small jobs get larger.
Is this subject included in your new mastercourse update?
No, this is outside the scope of the C# Mastercourse.
Can you please make some videos on xamarin mobile app development or apache cordova ?
I will add it to the list. Thanks for the suggestion.
What if I have an event that tells me that an employee has been added, changed or deleted so I can expire the cache Instead of giving a short time and the data is still not changed
is it a good practice?
Sure, just set the cache in that event and it will overwrite the current list.
@@IAmTimCorey Thank you so much
Great video
Thanks!
Humbly, thank you. :)
You are welcome.
@IAmTimCorey hey, mr Corey.. I am a South African that cannot afford your full courses... How's about a give away video? Hmmm 😁😁
May I ask you what is difference if I create a Singleton repository and load all data into some private field inside the class? can I imitate In Memory Caching using this approach? because every hour first I check the data Count first if there are something added to my data then I will reload my repository again
> because every hour ... I will reload
You can write... but do you need to write something? All already written and need just set 1 hour timeout.
> if there are something added
You can update your cache any time you want. It just hashtable in the memory - use the same key and replace the object.
@@AMurr-zm4wh if we set the Memory Expiry to 1 hour then after 1 hour we need to reload again (IO cost) but if I check just count of records every hour maybe I don't need to reload again for a couple of hours and it means less IO cost (I need to add new records to my pool only)
@@nadervaghari51
Ok.
Set 2 hour timeout and update cache in 1 hour. Take object out of the cache, add if you have something to add to the object and put it back into cache - this will reset the timer.
In this way you not need to write any additional code.
@@AMurr-zm4wh but the main question was can we use Singleton fields in place of In Memory Cache or not?
@@nadervaghari51
Yes, you can. At least I use it in the past in global.asax - there was no other way at time.
But main question is different - Why do you want to write and support additional code in place where nothing need to be written?
The title is slightly misleading. This is not C# in general, it is a specific use case stuck in the web mindset. Can you show us how this applies, for example, to WPF or maybe even Xamarin?
It is C# in general. I talked at the end about how you would use it in a desktop app.
Hi can Imemorycaching be used in webassmbly?
I believe so. Just remember that you are storing it on the client's machine so it will be client-specific.
Good job
Thank you!
How can I make it thread safe??
The cache is thread-safe.
Thank you!
You are welcome.
Sound is awful. I started to watch and had to switch off.
You can always turn on CC in UA-cam
The way how your explain caching here is much better than in your paid course webapi about caching, like here you even expain with blazor just like in real world so much better but WHY? @IamTimCorey. I Thought paid course could me litle bit more like this?
The course isn't about in-memory caching. The course is about the API project template. We cover a LOT of ground in that course, but we don't go into depth on things beyond the scope of the course. So yes, you will find more in-depth topics on this channel or in other courses that are more specific to the topic you are looking into. The API course goes into depth on API, not on all of the connected items. Otherwise, it would be a MASSIVE course. Also, the primary purpose of a course is to lead you down the path of learning a technology in a structured, ordered manner. That is the main benefit of the course. There will always be more depth to go into, more things to learn, and more areas to grow in after you gain the foundational knowledge of the topic.