3 ms·
You have to provide the events by yourself. See EventReduce as a simple function that can do oldResults+Event=newResults. And yes, you should always do testing
by eventreduce 6y ago
You have to provide the events by yourself.
See EventReduce as a simple function that can do oldResults+Event=newResults.
And yes, you should always do testings before you use open source stuff. There is no warranty use it on your own risk.
- ComodoHacker 6y agoOK, so you don't "tunnel writes through" EventReduce, you "tee" them to EventReduce. Anyway, to maintain consistency, you have to limit yourself to one process of your app. No sharding, load-balancing etc. This is significant limitation, and it's not obvious. I encourage you to mention it in README.md.
- eventreduce 6y agoI encourage you to read the readme and check out the demo. EventReduce is nothing magically drills out your database and affects the consistency of your write-accesses. It is a simple algorithm that is implemented as a function with two inputs and one output.