Indeed!

Azure Functions has been around for some time. Like AWS Lambda, it allows you to create the smallest piece of functionality for whatever code you need to build i.e. an API, a timer-based execution function and so on. Although you can build an extensive system with Azure functions, you can quickly become embroiled in some spaghetti code and communication between functions (similar to microservices etc.). Now, there is something called Azure Durable Functions - which I have to confess it has been a while since I looked into this, but the key aspect of durable functions was to orchestrate flow and so on between Azure functions.

Which now begs the question, using .NET Aspire within Azure Functions supersedes durable functions?

I am not sure, as I haven’t delved too deeply, but it certainly looks like a more modern approach to build distributed systems and, in this case, with Azure functions. This is not only available when building new Azure Functions, you can add the Aspire orchestration to existing functions too.

Hey, subscription to this podcast is FREE if you want to subscribe! I hadn’t realised before it forced you to pay ;) Of course, if you wish to or must pay, then please feel free with a paid subscription or via Patreon

Or just buy a unicorn a coffee here!

Oh, and yes, I have ended up on YouTube (doesn’t everyone eventually?):

https://www.youtube.com/@justfifteenmins but don’t worry, no ugly face to worry about (yet!).

Unicorn University:

https://applied-ai-services.kit.com/020c6040f2