Zulip's API is built on roughly this design pattern: * https://zulip.com/api/real-time-events https://zulip.com/api/real-time-events * https://zulip.com/api/r

Zulip's API is built on roughly this design pattern: * https://zulip.com/api/real-time-events https://zulip.com/api/real-time-events * https://zulip.com/api/register-queue https://zulip.com/api/register-queue * https://zulip.readthedocs.io/en/latest/subsystems/events-system.html https://zulip.readthedocs.io/en/latest/subsystems/events-sys... We use this same long-polling based /events API interface for all official clients (web, mobile, terminal), our interactive bots ecosystem (https://zulip.com/api/running-bots https://zulip.com/api/running-bots), and many integrations (E.g. bridges with IRC/Matrix/etc.). We also offer webhooks, because some platforms like Heroku or AWS Lambda make it much easier to accept incoming HTTP requests than do longpolling, but the events system has always felt like a nicer programming model. (Zulip's events system was inspired by separate ~2012 conversations I had with the Meteor and Quora founders about the best way to do live updates in a web application).