We are developing an ASP.NET web application on load-balancing system. Now we are facing several problems with current cache system:
Thanks.
Turns out that GCP's load balancer can easily cache common requests, and move them to Google Cloud CDN to reduce latency, as well as reduce the number of requests needing to be served by the instance. As long as the request is cached, it will be served directly at Google's network edge.
You can configure an Azure Redis Cache for an Azure-hosted ASP.NET Core app, and use an Azure Redis Cache for local development. An app configures the cache implementation using a RedisCache instance (AddStackExchangeRedisCache). Create an Azure Cache for Redis. Copy the Primary connection string (StackExchange.
Have seen NCache. It is free(the Express version. For Professional and Enterprise just Developer Machine is free ) and asp.net compatible.
NCache is an extremely fast and scalable in-memory distributed cache that caches application data . NCache also stores ASP.NET Session State Sessions in web farms. Works grate with Loadbalancer and simple to configure.
We use memcached and have had no problems with it. Very reliable and pretty simple to implement. What do you mean you'll have a bottle-neck problem with a third party caching solution? We've been running it for about a year or so now and have had great experience with it.
Edit: Our environment is load balanced across 3 web servers and 2 SQL servers.
The other reason I would prefer third party is because you can cache anything in it, objects, data, etc.
Setup: http://syntaxhelp.com/ASP.NET/Cache/memcache References: http://code.google.com/p/memcached/wiki/NewStart
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With