Where is the best place to keep a "hot cache" in a .net service?

Question

.NET

There is a service written in .net c#, there is a database that stores data.
There is a layer of data that is used quite often and, accordingly, is loaded from the database, which is why performance sags. There was an idea to take out this data in a cache. The question is which is better to use? Storing data in collections of objects in the service itself is not an option. There was an idea to use ElasticSearch for this, is this a good option? What are the alternatives?

Answer 1

And why do you like radishes not radishes? Or another classic ?

Answer 2

You can consider https://msdn.microsoft.com/ru-ru/library/system.ru...
You can use Redis through the stack of libraries from StackExchange - https://github.com/StackExchange/StackExchange.Redis
You will also need it there serializer for cache values, you can use something like https://github.com/kevin-montrose/Jil (or look here https://nickcraver.com/blog/2016/02/17/stack-overf.. . )