3 ms·
Like I said, I was going to break your assumptions on data systems. Treating data as mutable (whether you use MVCC or append logs or any other approach) leads
by nathanmarz 15y ago
Like I said, I was going to break your assumptions on data systems.
Treating data as mutable (whether you use MVCC or append logs or any other approach) leads to major complexity problems, as I detailed in the post.
- ww520 15y agoRedefining the meaning of general term just creating more confusion about the point you want to make. Why not use precise definition. The term "data" is really really general and it's bad to convey what you really mean. Are you talking about data value? Data object? Data record? Data version? Data event? Quoting from your blog, "A piece of data is a fact that you know to be true at some moment of time." That's called an Event. That's a snapshot of fact in time. MVCC is one way to do transaction. The blog didn't deal with transaction at all so I don't see the comparison. Append log-based databases do the closest to what you described in avoiding changing data in place and recompute/precompute data at query time. It's a very simple mechanism. What complexity problem do you see with it?