serializability and consistent pagination

I like the interleavened tables idea - seems it could work well with DDD aggregates. I guess for 3 I was thinking some sort of mvcc snapshot based approach although I can’t imagine comes too cheap if data is changing frequently, but curious how you keep reads performant with strict serializability guarantees? I do like the idea of being able to easily have subscriptions to changing data and I assume that’s a big part of what your pushing out to those edge servers re: TCP connections?
Was this page helpful?