I'd agree and would also like to see a Reliable FIFO stack and Hashtable
Oh and Azure IoT Edge is nice ;) https://blogs.microsoft.com/iot/2017/05/10/microsoft-azure-iot-edge-extending-cloud-intelligence-to-edge-devices/
have you seen this https://twitter.com/kobajagi_doktor/status/912757250598559750 ;)
just and idea; if ServiceFabric could host something like allowing AzureFunction that would be a good solution IMHO as long as it was available to on-premise/cloud linux/windows c#/java
Please consider custom triggers for example SQL/Oracle database change notification or SMS triggers for on premise or ServiceFabric actor activation activity
FYI, I'm currently using a ReliableCollection to inform the instance of the service to shutdown; where the service upon seeing the update use/sets the CancellationTokenSource thus causing the shutdown.
ServiceFabric application configuration has a service instance; this can be removed to stop the deployment creating instance(s) of the service
Thank you for the feedback. We will look into this.
I believe that nginx running I front of the service fabric cluster would be a good options as a first step; this is a software configurable loadbalancer/reverse proxy the has an api which can be used to update the configuration as/when required by service fabric. IMHO writing an software defined network is not a service fabric task, but service fabric would definitely benefit from communication with a software defined network api that would allow for confirming nlbs etc..
Azure Cosmos DB is a multi-model database service, and therefore supports accessing the same underlying data using any/all APIs. We are however implementing some platform-level changes to make data access from different APIs seamless like supporting conversions between disparate type systems, and capabilities.
This feature is currently in active development. We will update this item to complete once it has shipped so those voting/commenting will be notified.
Thank you for your patience.
Reopening this user voice item as our support for Skip/Take (Offset/Limit) was only limited to single partition queries.
The newly released .NET SDK v3 now includes support for x-partition queries using Offset/Limit. You can learn more about v3 SDK and try it and provide feedback on our github repo here.
We will also be back-porting this functionality to our .NET v2 SDK. This work will begin shortly and we anticipate it to be released in September.
Once that is released we will mark this feature as complete.
Thank you for your patience and votes.
Apologies for the confusion on our part.
This is currently not on our roadmap. However, we will review this item in the future as we prioritize future releases.
Thanks for your suggestion.
would this be a good fit for serverless functions? which are is essence a layer above the underlying data store?