Two ways • Azure Logic Apps: For those who like user interfaces and workflow definition files. • Azure Durable Functions: For those who like codifying workflows, and more.
Workflows you said? • Define workflows in code. No JSON schemas or designers are needed. • They can call other functions synchronously and asynchronously. Output from called functions can be saved to local variables. • They automatically checkpoint their progress whenever the function awaits. Local state is never lost if the process recycles.
Problem 1 : Function Chaining • No visualization to show relationship between functions and queues. • Middle queues are an implementation detail – conceptual overhead. • Error handling adds a lot more complexity.
Problem 2 : Fan-out/Fan-in • Fanning-out is easy, but fanning-in is more complicated. • Functions offers no help with this scenario today • All the same problems of the previous pattern
Why Logic Apps? • Saving time by designing complex processes using easy to understand design tools • Implementing patterns and workflows seamlessly, that would otherwise be difficult to implement in code • Rich Managed Connectors
daronyondem
mixi_engineers
bumptakayuki
non97
mochico
matsuihidetoshi
mhidaka
masakamayama
_kensh
miyake
keio_smilab
nagix
philhawksworth
akosma
chriscoyier
notwaldorf
dougneiner
lauravandoore
samanthasiow
samlambert
frogandcode
keavy
reverentgeek
danielanewman