I was recently looking for a simple in-memory caching library that sat on top of ConcurrentDictionary. I didn’t have many requirements other than it needing to be thread safe and and had some expiry policy built-in. I’ve used .NET MemoryCache before, but figured there likely had to be something simple else already built. My search led me to Foundatio:
Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling. Get started for free.
BasicsCaching in it’s various forms (in-memory, distributed) is simply about storing a copy of the data in a way that improves performance. This could be data from a web service, database, or any other call that involves reading data that rarely changes but is read/queried often.
FoundatioFirst thing will be to get the latest NuGet package.
PM> Install-Package FoundatioThere are many other components that Foundatio provides besides Caching, such as: Queues, Locks, Messaging, Jobs, File Storage, Metrics and Logging. I haven’t dug into any of these other areas yet, but once I do, you can expect a blog post.
In-Memory Caching Demodemo application on GitHub. This demo console app is going to show currency exchange rate between USD and CAD for a given day. Since historical exchange rates don’t change, there is no point in making an HTTP call for a day that was already queried. Also, one really cool feature I’ll show, is that you can set the max number of items in your cache. So for this demo, I’m only going to keep the last 3 exchange rates by date in cache. First we can start off by creating a new instance of an InMemoryCacheClient and setting it’s MaxItems property to 3. Next, I want to create a method that is going to query for the exchange rate, but before it does, I want to check the cache to see if it exists. The key for our cached object is going to be the date. If the key does not exist in the cache, then we will make our HTTP call, get the results and cache it. Now to write this all up, I’m going to take a date as input from the console application and have it invoke our GetCurrencyRate(DateTime).
ResultNow when we run our application, we can see that if we request the same date, within the last 3 requests, we will hit the cache instead making our HTTP call.
- Requested 2016-01-01, 2016-01-02, 2016-01-03, all of which were fetched from HTTP service.
- Requested 2016-01-01 again, which was pulled from cache.
- Requested a new date 2016-01-04 which was fetched from the HTTP service.
- Requested 2016-01-02 again, however since it is no longer the last 3 requested (2016-01-03, 2016-01-01, 2016-01-04) it has to fetch from the HTTP service.