There is a document on the subject, but it's lacking in a few ways:

• It does not state what exactly the default placement strategy is.
• It does not state whether one can override the default strategy for all grains.
• It does not explain how each of the built-in strategies work ([random, prefer local,

Which project template is the issue about?
API
...

Which version of the project template is the issue about?

...

Which version of Visual Studio or the dotnet SDK were you using?
2.2.203
...

If you call the API with a client and you set Accept to application/json it is completely ignored and you will ALWAYS get application/vnd.restful+json back.

Is this desired?

As we plan to enhance CRDs with features and to avoid breaking changes to actually break things, we should use version fields of all CRDs inside the codebase to control at which version some features would be enabled or not.

An example of some enhancements I envision are:

1. Automatic health report/check
2. Placement constraints + heterogeneous clusters
3. Metadata

ASP.Net Controllers has the ability to read [ProducesResponseType] and generate swagger.json which is used to renger Swagger documentation pages.

To support that Json generation we need:

• Add attributes that mimic that behaviour without having the MVC dependency
• Extend Swashbuckle package (create Swashbuckle.Orleans?) to read from those attributes and generate the swagger.j

Currently the whole Dictionary<XName, InstanceValue> in IWorkflowState is serialized with NetDataContractSerializer and zipped with GZipStream. NetDataContractSerializer uses XML format (XmlDictionaryWriter). We should try to use Orleans or any other serializers.
NOTE: One of the special values in InstanceValue is the ActivityExecutor itself, and it's allegedly works only with

Boban @bobanco 00:01

@creyke wouldn't be easier to implement the saga on a top of EventSourced grain?

Roger Creyke @creyke 00:02

if the saga is a "true" saga, the result of the work is inconsequential
for me, that would be "adding a log"
which is sure, optional
and probably a good feature

It seems as if there are methods being used by Orleans.CosmosDB that are no longer existing within the 2.x version of Microsoft.Azure.DocumentDB.Core. We should probably patch the nuget package to prevent folks from using v2.0, v2.1, or v2.2 of Microsoft.Azure.DocumentDB.Core. As a subsequent patch, this library should go to v2.0.x and be upgraded to the v2.x Microsoft.Azure.DocumentDB.Core.