azure-service-fabric

I would like to use service fabric reliable dictionaries to store data that we intend to query via a rest interface. I was wondering what was the most optimal approach to querying data held in those collections. The documentation doesn't seem to provide any methods to support querying a IReliableDictionary interface apart from simply enumerating over the collection. Is the only option to fetch every object out of the reliable dictionary and pop into a List<> collection for querying? Thanks As Vaclav mentions in his answer, you can always enumerate the entire dictionary and filter as you wish.

I want to migrate typical windows service which is written in .net to Azure using Service fabric. To implement this , I am creating one service fabric application containing one micro service as guest executable which uses .exe of windows service and deploying application package to service fabric cluster. After deploying service fabric application on cluster I want windows service should install & start automatically on all nodes however at any time application is running on any single node. I want windows service should run on only one node at a time. Please kindly help to implement this.

I'm building a small service fabric maintenance in aspnetcore (dotnetcore2.0) application but now doesn't recognize the UserPasswordCredential class. From here it is by design as they say. With that I need to convert my previous code so that I can create a valid FabricClient. How I can convert the GetAccessToken() method? private static FabricClient CreateSecuredFabricClient() { try { var claimsCredentials = new ClaimsCredentials(); claimsCredentials.ServerThumbprints.Add(_sslThumbprint); var fc = new FabricClient(claimsCredentials, _clusterConnectionString); fc.ClaimsRetrieval += (o, e) => {

I have a scenario where we need to store x*100 GBs of data. The data is in-general a good candidate for persistent state for an actor (well-partitioned, used by the specific actors only) in the service fabric cluster itself. Is the service fabric persistent state storage recommended for data of this scale? (Our compute load is going to be fairly low, so bumping up VMs just to store the state is not a desirable option.) How does the amount of persistent state affect the latency of moving partitions between nodes in the cluster? Well let's look at how state is stored in a service (this applies

EDIT 04/06/18 => Updated question with last status So I have this working .Net 4.6 Stateful Service that currently run on my Windows Service Fabric cluster deployed on Azure. Starting from 09/2017, I should be able to move to Linux: https://blogs.msdn.microsoft.com/azureservicefabric/2017/09/25/service-fabric-6-0-release/ So I'm trying to deploy it on Linux so I can save costs. First things first, I've migrated all my code from .Net 4.6 to .Net Core 2.0. Now I can compile my binaries without issues. I've basically created new .Net Core projects and then moved all my source code from .Net 4.6