Is there a recommended way work with blobs as reliable state in Azure Service Fabric?
I see two options:
Implement a chunking mechanism and store chunks in a reliable collection. This option has a pretty heavy development/maintenance burden though.
Store blobs externally (Azure Blob Storage). This option couples the service with Azure though. We would have to provide our own abstraction and implementation for running in an on-premises cluster.
Maybe there is a reliable state provider/manager for blobs already available somehow?
Those are your two best options currently. There isn't a blob state provider or service built in today. If you do store blobs in reliable collections, I would recommend chunking to reduce replication traffic. You may even consider building a blob storage service that uses a reliable dictionary to store chunks, deploy the service with multiple partitions for better distribution, and then provide a client for it that takes a blob, chunks, and distributes.
The web app example backups and restores a service state in a blob storage. You can do the same if you inherit from ActorService instead of Actor. So you are able to make backups to azure storage.
I implemented for my company a failover system which backups in a blob storage. The storage is relativly slow, so it is not recommended to use it as default state location.
来源：https://stackoverflow.com/questions/36395536/reliable-blob-state-in-azure-service-fabric