What are the good use cases for these ?
What are the good use cases for these ?
Is there a better way to this ?
Ideally, we should persist the Object Graph directly without any data conversion. I see a difference in - How we compute and How we store data.
I do store the entity data separately in a transactional row store.
For analytical queries, we use a column store. For this, I have to include the entity data (context) for each fired event.
The whole Compute & Storage semantics are different.
If only, we had a persistent data-aware compute & storage graph engine that supported transactional & analytical workloads.
If you look at data historians (PI et al), that's how they lay out the data: metrics storage is separate from the asset store, or Asset Framework as it's called.
tracking goods (amazon uses a gigantic graph database to track everything in its warehouses throughout the goods' lifecycle)
network analysis
Could you elaborate on this? Are there any articles/papers on this topic?