Synchronization

We call our synchronization mechanism seq because it fetches a sequence of events.

At its core, synchronization simply entails calling seq in an infinte loop, where every call to seq uses the "seq" value returned from the previous call. That is obviously very inefficient, so to address that we have a service called ping. Whenever a change happens in our database, we will send a ping request to a URL of your choosing. This is your prompt to call seq.

There are two hard problems in computer science: cache invalidation and naming things. The requests are simple but synchronization is extremely difficult and full of pitfalls. For a deep dive into the intricacies, see the implementation notes. It's long and boring and extremely recommended reading.