All geek questions in one place

Using RavenDB as a persistent cache

I currently have a web application that caches a large amount of data (several hundred thousand records) in memory for quick retrieval, and then in SQL Server as a persistent cache. Basically, the information consists of address geocodes, where the geocode is retrieved through a remote web service, which takes time, if necessary, to call continuously, rather than caching.

Would using RavenDB (or other suggestions) be the best way to cache this information in persistent storage in terms of speed and memory? Currently, the application is hosted on a server that SQL Server sucks up most of the memory, so I would like to get an easier solution.

+2
source share
2 answers

RavenDB as a document database seems redundant to me if it is used only as a cache. What about redis as a value store? This may be better suited to what you are after.

0
source

RavenDb should be faster to read than SQL. Not that the record is slow, but it is optimized for read operations as far as I know. So you should try, it should be better in terms of performance. However, I am not sure of the memory.

If you need more information, you can always try the RavenDb Google Group . Ayende follows him so that he can answer himself.

0
source

Source: https://habr.com/ru/post/1398729/

More articles:


All Articles