in favor of minimal durable functions, like minimal api for mvc but longer running

[vigouredelaruse]

problem statement:
when using durable functions developers have to

• implement their own activity scheduler
• police their own compliance with durable function orchestrator code constraints
• simultaneously lean on at least 2 disciplines;
  • orchestration scheduler developer
  • workflow activity developer

suggestion
developers should be able to

• depend on activities called by intrinsic 'infrastructure' schedulers, presumably configured by providing a (json) graph, like in logic apps
• shed the cognitive load of 'properly' implementing a durable function scheduler
• leverage a built in set of scheduling patterns as per the documentation
• leverage 'minimal-code' semantics without necessarily actually setting low-code semantics as an explicit goal

scenario a

• user provides graph depicting sequence
• user provides configuration of orchestrator pattern desired
• user registers 'meta' orchestrator in dependency injection
• here it gets hazy
  • user injects meta-orchestrator into a starter function and provides the required configuration to the meta orchestrator
    • user observes meta-orchestrator logging and activity logging by the usual means
  • user injects meta orchestrator into an orchestrator function that is essentially a thin facade
    • user provides orchestrator function inputs to meta orchestrator and observes as usual

scenario b

• this all works by providing visual studio project templates of boilerplate orchestrator pattenrs
• this all works by templated code generation that is more aware of the domain than a project template

in longer back of the napin form we're talking about

• provide the graph of activity sequencing. for this i'm going to simply paste in the json for a logic app orchestration from the documentation. let's not ignore the dsl directives in the sample because somebody thought they might be a good idea
• to diminish the typing involved in this scenario the possibility is there to render this json using
  • a builder pattern
  • builder would permit typesafe crosscutting concern referencing of orchestrations, activities, dependencies and the proposed scheduler mechanism

{
  "$schema": "https://schema.management.azure.com/schemas/2016-06-01/Microsoft.Logic.json",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "order": {
      "defaultValue": {
        "quantity": 10,
        "id": "myorder1",
        "companyName": "NAME=Contoso"
      },
      "type": "Object"
    }
  },
  "triggers": {
    "request": {
      "type": "Request",
      "kind": "Http"
    }
  },
  "actions": {
    "order": {
      "type": "Http",
      "inputs": {
        "method": "GET",
        "uri": "https://www.example.com/?id=@{replace(replace(base64(substring(parameters('order').companyName,5,sub(length(parameters('order').companyName), 5) )),'+','-') ,'/' ,'_' )}"
      }
    }
  },
  "outputs": {}
}

how many more orchestrators do you plan to write yourself, or direct to be re-implemented yet again
regards