The difficulties around webhooks, and pub/sub in general on the web, is a great example of how decentralized architectures can make things much harder. I wonde

The difficulties around webhooks, and pub/sub in general on the web, is a great example of how decentralized architectures can make things much harder. I wonder about an alternate timeline where someone had cornered the market on pub/sub as a service, a centralized pub/sub system that everyone goes through, kind of like how Google and Apple have a duopoly on push notifications. Imagine this: 1. You are sending out emails through an email service provider (Mailchimp, Braze, etc) and you want to subscribe to an event stream of success/failures/errors/etc 2. You register with the email provider and they hand you back a token for SassyPubSub 3. Your backend service registers its token with SassyPubSub and lets it know exactly how you want to be notified - posts to a URL, over a persistent websocket connection, pushes to SQS/RabbitMQ, etc 4. The email provider pushes messages to SassyPubSub 5. You consume those messages however you want. The flow should be dirt simple, just a few lines of code to setup. To be effective, it'd have to have industry wide standard adoption, but it would simplify so many things.