I am working on a project in which I need a set of data frequently and currently for getting that data I have to make call to 3rd party Service which is taking lot of time.So what I want is to maintain a local cache.The Data is modified very infrequently or is almost constant.What is the best way of implementing this in Azure Service Fabric.I am currently thinking of making the Microservice stateful. Is is the best way to do this?When node goes down it should copy its local cache to other node.If making it stateful is good than How should i go on implementing this?
相关问题
- running headless chrome in an microsoft azure web
- Docker task in Azure devops won't accept "$(pw
- Register MicroServices in Azure Active Directory (
- Removing VHD's from Azure Resource Manager aft
- Cannot use the Knowledge academic API
相关文章
- Is there a google API to read cached content? [clo
- SQL Azure Reset autoincrement
- How to cast Azure DocumentDB Document class to my
- Can't get azure web role to run locally using
- Azure WebApp - Unable to auto-detect the runtime s
- How to change region for Azure WebSite
- Azure webjob vs cloud service
- Azure data transfer Identity Column Seed Jumped by
I know this post is quite old, but for those looking for a solution today, you can use this open source project:
http://service-fabric-distributed-cache.socreate.it
you can also find it on GitHub here: https://github.com/SoCreate/service-fabric-distributed-cache
Well, you have two options: If you need performance and geografical cache data replication, you can use a redis cache.
The other option is use reliable dictionary's. It's a service fabric feature, and reliable dictionary's are replicated to other nodes.
You can only access the reliable dictionary in a service fabric statefull context.
Example bellow: