Funny because in the current b2b fintech project I work at I designed all protocols with /events (long-poll), but later everyone asked for a webhook instead. And their API is full of webhooks. It feels like people who build these systems don't bother to implement event streams.
What makes you think they don’t implement event streams? The webhook is just an entry point at the edge of their application. It could easily be writing to a queue or some message broker. It’s simply easier when doing eg serverless because it’s hard to keep that long lived connection for indefinite amounts of time versus simply exposing a stateless HTTP API.
This is an interesting idea, but why don't they just use the outside service as a queue, because it works as one, and when it doesn't, this complete direction doesn't work either.
easier when doing eg serverless because it’s hard to keep that long lived connection for indefinite amounts of time versus simply exposing a stateless HTTP API
You mean "functions" or a similar thing? It may be the reason I think. I didn't know that serverless discourages using idle persistent connections.
It’s not so much that it discourages it’s more of a case of it simply won’t work because most functions have a timeout and are stopped after a few minutes at most.
