News for hackers. Stuff that matters.
Re:Call me maybe: Aerospike by hurin on Tuesday May 05, 2015 @10:59PM (#9496369)
> A better example is frequency capping. Ever watch something on Hulu and see the same ad 4 times in a twenty-minute commercial? Or even, worse, back to back?

Yeah, but when that happens I usually don't think, oh hey they are lacking an optimal in memory distributed database solution.

I think, well... their engineers suck. Or they don't care. Pick one.

edit: His point is vague, so there is nothing technical to respond to. I am very much interested in a good technical example - but the things mentioned so far are by all appearances relatively straight-forward and linear, hence lack of effort or bad engineering are the only reasonable assumptions left.

Re:Call me maybe: Aerospike by cwyers on Tuesday May 05, 2015 @11:14PM (#9496411)
I don't get your point here. He's explaining why it works the way it does. You're saying you don't think about it as a user. That doesn't invalidate or even respond to his point.
Re:Call me maybe: Aerospike by phamilton on Wednesday May 06, 2015 @01:46AM (#9496772)
Volume and latency requirements make it more difficult to track individuals on the web. It's an easier problem to solve in 50ms. It's also much easier to solve when it's only a million individuals rather than a couple hundred million individuals.

Like most problems, scale makes it hard.

Re:Call me maybe: Aerospike by hurin on Wednesday May 06, 2015 @03:07PM (#9501055)
It's simply not a difficult problem: there are no consensus requirements between individuals, so scaling can't be made any harder by increasing N.