Ahhh you know what, I should call it stream processing or something, because we don't store the data entirely as events. We store the data as a mutable K/V which emits an event stream of changes, which can then be ingested into different views. We chose not to store changes as events specifically because we don't want unbounded growth in the system. Initial syncs work by fetching the current state of the K/V store (the "data repo").
Bluesky is built on atprotocol (atproto.com) and can be thought of as an open distributed system. The event stream is for replicating throughout the various services.
Bluesky is built on atprotocol (atproto.com) and can be thought of as an open distributed system. The event stream is for replicating throughout the various services.