Currently the only index available is by entity_id and domain. Any other bulk operations rely on key listing (which is fine for lower scale / operational only use cases).
If perhap wants to replay events and provide more functions in the "event store" sense, it needs to build smarter indexes around events by time periods within the realm or context stored.
This would allow the SLA between reducers and platform to be more specific on the topic of state lifecycle and better target reducers for specific workloads.
Currently the only index available is by entity_id and domain. Any other bulk operations rely on key listing (which is fine for lower scale / operational only use cases).
If perhap wants to replay events and provide more functions in the "event store" sense, it needs to build smarter indexes around events by time periods within the realm or context stored.
This would allow the SLA between reducers and platform to be more specific on the topic of state lifecycle and better target reducers for specific workloads.