All geek questions in one place

Appfabric caching: configuration provider as a single point of failure

After an initial study of using Appfabric for caching, I understand that the configuration provider for the cluster is the only point of failure, as indicated here:

MSDN

I want to use appfabric only for distributed caching, especially for tag functions. What are the options to prevent using the configuration provider as this point of failure? I was thinking of two, but not sure if there are any better or better options.

(1) Create your own caching service configuration provider. I guess this is possible (?), But I'm not sure how to do it. I would probably make a provider that extracted the XML file from S3, since I already use AWS.

(2) Configure each cache as a single node cluster, and then create a proxy client that uses the individual nodes as a distributed cache, the la-memcached client.

Thoughts or recommendations or something else that I should consider when making this decision?

+3
source share
2 answers

Yes, this is the only point of failure.

Recommended Microsoft solutions are as follows:

  • (SQL Server Provider) Use SQL Server clustering. In my limited experience with SQL Server, clustering for this is probably the case of a “cure worse than a disease, that is, it brings a lot of pain. If you no longer have SQL Server cluster available, avoid it!”
  • (XML ) Windows Server . , SQL , , ( ) . .

, ICustomProvider . AWS , , , .

- , , , AppFabric, .

+3

AppFabric, , , , API, . NCache, , AppFabric. NCache .

+1

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

More articles:


All Articles