Show HN: Jet – in-memory, fault-tolerant, distributed stream processing

Re:Show HN: Jet – in-memory, fault-tolerant, distributed str... by haxen on Wednesday August 12, 2020 @07:28AM (#24130896)

This statement comes from our benchmarking work:

https://jet-start.sh/blog/2020/06/09/jdk-gc-benchmarks-part1

The point is that Jet can track several million distinct keys, even on a single machine, and finding velocity vectors boils down to linear regression sliding window against two FP variables.

If your concern is why you would specifically want to track locations, the answer is that there are plenty location-based apps that track locations with user's consent.

[ Parent | on HN ]

Re:Show HN: Jet – in-memory, fault-tolerant, distributed str... by jmnicolas on Wednesday August 12, 2020 @08:48AM (#24131500)

Yes my concern is about how casual you sound about tracking millions of GPS locations.

By user consent you mean someone clicked a button without thinking to get to the app ?

[ Parent | on HN ]

Re:Show HN: Jet – in-memory, fault-tolerant, distributed str... by haxen on Wednesday August 12, 2020 @09:09AM (#24131674)

Here are some examples where user consent is undisputed: ride hailing, bicycle rental, street navigation, running/biking/sailing contests, location-sensitive searches. These are the kinds of applications for which Hazelcast Jet offers easy scaling into millions of users.

[ Parent | on HN ]