Service Fabric Mesh with SignalR Service

Question

Can you share a ReliableCollection between Service Fabric Mesh and the Managed Signal R Service. If not what other options are there for a distributed key/value store that would work across Azure. My original design was the App Service + the Managed Signal R + Functions, so something that works with all three would be good. I could use the Azure Cache (Redis) as a backplane but this doesn't seem the best option (data needs fast reads, writes happen much more infrequently).

I could create my own but would prefer something built in if possible. If there is nothing suitable as a side question what would the typical latency be on Event Grid, is this reliable and quick enough to use as a basis of coordinating a quorum of microservices? Really looking to keep it all as flexible as possible.

Thanks

Answer 1

• have a look at the Azure App Configuration which can be used for distributed metadata driven architecture as an option what you are building.
  • The Azure Event Grid (AEG) is the Pub/Sub eventing model for reliable distributing of the event messages in the Push Fan-Out manner. The publisher latency is ~50ms. Note, that the AEG doesn't guarantee distributing events in an order how they was published (emitted to the AEG)

Thanks
Roman

Answer 2

Service Fabric Mesh, unlike Service Fabric, is more similar to a container orchestrator like Kubernetes. And it does not support ReliableCollections. Instead, it supports Volumes as mentioned in the docs, with the option for Service Fabric Reliable Volumes or Azure File Share Volumes.

Considering your use case, Redis would be the best external distributed store for you to leverage as a in-memory data structure store. But you should be able to use any data store depending on your exact requirements.

Also, you could consider using dapr, a distributed application runtime, which shares many aspects with service fabric while being language agnostic.