Azure: Redis vs Table Storage for Web Cache

Question

We currently use Redis as our permanent cache for our web application, but with it limited memory and cost. I am starting to consider whether table storage is viable.

The data we store is pretty simple json data with a clear 2-part key, which we will use for the section and row of the row in the table storage, so I hope this will mean a quick request.

I appreciate that one is in memory and one is because storing tables will be a little slower, but as we scale, I believe that there is only one processor that serves data from the Redis cache, whereas with the table storage, we would not have such a problem as it would be less than the number of web servers on which we work.

Does anyone have any experience using table storage this way or comparisons between them.

I have to add that we use Redis in a very minimalistic way get / set and nothing more, we evict our own data and fail that leave Redis evicted when it runs out of space.

Answer 1

. , , , :

• - /. , . .
• 500 .
• Redis ( Redis Service). , 2000 / , 20 000 / , .
• , VM Redis.
• Redis Azure Storage (, pub/sub, ..).
• , Redis , SDK API.

Answer 2

redis , , . Azure Redis, redis 50- . , . , .. , . details. , redis.