As with database normalization, it is a good idea to first do it as much as possible, and then denormalize again until it is fast enough.
As with database normalization, it is a good idea to first do it as much as possible, and then denormalize again until it is fast enough.
Essentially, you keep the DB in a normalized state. You define views of the DB that you want. Then the DB keeps those views as tables for you, and the DB does all of the hard work of keeping those view tables consistent with the denormalized data. Essentially the DB does the atomicity, cache-invalidation, and cache-updating for you.
You get performance, and you get the certainty that invalid states are un-representable.
I guess the biggest blocker here is in automatically determining what fields do and do not need to be update automatically?
https://github.com/mit-pdos/noria
https://corecursive.com/030-rethinking-databases-with-jon-gj...
https://notamonadtutorial.com/interview-with-norias-creator-...