3 ms·
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 w
by TrueTeller 8y ago
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-functions-645ecb3c1d58 https://hackernoon.com/making-sense-of-azure-durable-functio...
- macca321 8y agoCool - 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.
- macca321 8y agowhoops 202 Accepted :D