Durable Function in Azure Function

Anonymous
2021-11-08T23:57:55.783+00:00

I am trying to figure out requirement for my project.

Based on feedback from the community, if it takes more than 230 seconds, it is better to use Durable function than using a regular HTTP Trigger.

My requirement is just pulling data from other third party API using HTTP, store data inside Azure SQL and use the data for reporting (Power BI) at the end.

Honestly, I am not sure how long it would take to pull data, but I guess I would just start with a safer (Durable function) approach.

So, I thought diving into Durable would be a better option. Is it?

From Youtube that I watched, it appears that it is more like "Http-based Async Long-running APIs" from scenarios of Durable function.

147561-image.png
Am I on the right approach?

Thank you.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,249 questions
0 comments
Accepted answer
  1. Mike Urnun 9,666 Reputation points Microsoft Employee
    2021-11-09T04:13:03.38+00:00

    Hello @KingJava - You're absolutely on the right approach. Durable Functions is for long-running, stateful workflows and you can utilize the Function Chaining pattern to organize the workflow where each Activity can be: Pull data from API, load data to SQL, etc.

    1 person found this answer helpful.
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-11-09T06:12:48.7+00:00

    @Mike Urnun Thanks for your response.
    I am actually still very lost on my architecture.

    So, basically, I am trying to pull data from a third party thru web service only once day.

    After discussing with my manager, I think I am currently leaning toward using Timer Trigger (due to smaller size of data) instead of using Durable, but if the coding is not too complicated, maybe using durable is not a bad idea.

    0 comments