3 ms·
I was under the impression that Percolator was a purely incremental system. I'll have to give the paper another read to see if they're using a hybrid batch/real
by nathanmarz 15y ago
I was under the impression that Percolator was a purely incremental system. I'll have to give the paper another read to see if they're using a hybrid batch/realtime approach.
The system I described isn't limited to any particular "type" of query. It's a way of supporting arbitrary queries on arbitrary data, which encapsulates everything.
Most people assume mutable state and incremental updates when building data systems. This is in fact the approach that almost all databases take. These are the assumptions I challenged.
- VladRussian 15y ago>Most people assume mutable state and incremental updates when building data systems. This is in fact the approach that almost all databases take. These are the assumptions I challenged. it isn't assumptions. It is requirements for some systems. You drop requirements - you get a breathing room and can build a different system.
- nathanmarz 15y agoMutability and incremental updates are never requirements. Requirements have to do with performance and resource usage: X amount of space, Y amount of memory, Z amount of latency, etc. Mutability and incremental updates are approaches. I showed a different approach with immutability at the core which leads to a system with some amazing properties.
- eru 15y agoI hope that examples like this and git make more people see the value of immutability. In the context of functional programming the same concept is called purity.