For example, what inspired this over a typical paginated API that lets you sort old to new with an afterId parameter?
What is the intention there though. Is this for social media type feeds, or is this meant for synchronising data (at the extreme for DB replication for example!).
What if anything is expected of the producer in terms of how long to store events?
Use HTTP server-sent events instead. Those can keep the connection open so you don't have to poll to get real-time updates and they will also let you resume from the last entry you saw previously.
https://developer.mozilla.org/en-US/docs/Web/API/Server-sent...
I would also rather not have a handful of long-polling loops pollute the network tab.
(Details in the previous thread on HTTP Feeds: https://news.ycombinator.com/item?id=30908492 )
I believe cloud events are most common in Kafka-adjacent or event-driven architectures but I think they're used in some GCP serverless things, too
If instead the client paginated by lastEventTimestamp, then a server that for any reason no longer had a particular event UUID could at least start at the following one.
sea-gold•15h ago