In my previous description, I avoided talking about atproto details for clarity, but this is all part of that (atproto.com). The "kv stores" are what we call data repos[1] and they use sqlite for storage, but can produce individual event streams. Those streams flow into the golang event stream, aka the "relay". View computation happens continuously.
1. data repos are actually signed merkle trees, which gives at-rest authentication of the data as it gets shipped across organizational boundaries
1. data repos are actually signed merkle trees, which gives at-rest authentication of the data as it gets shipped across organizational boundaries