Migrating to Durable Function

Question

I have a non-durable pipeline of three Azure Http Trigger Functions. They pass along a custom json graph in a sequence.

I have started to migrate this to Durable Functions (using the sample as a basis) and it appears that I can just pass the json graph around as a string without using Task<HttpResponseMessage> etc.

Is this the best way with Durable Functions. Could I still keep each function as a HttpTrigger in order to have the flexibility of calling the whole pipeline as Durable but each individual as an HttpTrigger?

jeffhollan · Accepted Answer · 2017-11-16 13:39:58Z

1

Each function needs to have an ActivityTrigger to work with Durable Functions - and we do not support having multiple triggers for a single function. To keep both options (HTTP Triggered or as part of a Durable orchestration) you would likely need to factor out the common code into a shared method that each function can invoke.

answered Nov 16, 2017 at 13:39

jeffhollan

3,22717 silver badges19 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Migrating to Durable Function

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related