Event Store Design/Implementation Requirements
Flexible partitioning of event components to different streams based on access characteristics
Support for both IDL-defined data structures and an OO event model, compatible with Fortran => C++ migration
Robust schema evolution (new codes reading old data and vice versa)
Easy management and navigation; dynamic addition of event components
- Named collections of events, production- and user- defined
- Navigation from from a run/event/component request to the data
No requirement for on-demand access
- Desired event components are specified at start of job, and optimized retrieval of these components is managed for the whole job (Grand Challenge)
- On-demand access not compatible with job-level optimization of event component retrieval