Re:A Fairy Tale of F# and Durable Functions
by TrueTeller on Monday January 14, 2019 @10:53PM
(#18908748)
Hi, the author here. It's a good point and a valid concern, but I did an explicit choice here: I didn't want to make the article longer.
I have a prequel post which describes my thinking of why durable functions make sense, including a primer for the event-driven approach: https://hackernoon.com/making-sense-of-azure-durable-functio...
[ Parent
| on HN ]
Re:A Fairy Tale of F# and Durable Functions
by macca321 on Thursday January 17, 2019 @11:07AM
(#18931831)
Cool - so that article you link sets the context for the second.
I do think it does HTTP a disservice though - when you switch from HTTP to EDA you ditch the well known Uniform Interface and a lot of the benefits you get for free,(i.e. robust caching/proxying/routing, all the things a Service Mesh can do).
Instead of ditching HTTP, it would be nice to see people building async HTTP APIs, where the API responds with 201 Accepted (probably using a message queue behind the scenes) rather than the brittle systems you describe, where everything comes back under a 200.