News for hackers. Stuff that matters.
Re:Ristretto: A High Performance, Concurrent, Memory-Bound G... by marktangotango on Saturday September 21, 2019 @10:58AM (#21035733)
Does anyone know of a similar cache that lets you restrict memory usage by “customer” for example? I used redis scripting to implement this use case in redis, it really feels like a hack though.
Re:Ristretto: A High Performance, Concurrent, Memory-Bound G... by hinkley on Saturday September 21, 2019 @07:19PM (#21038521)
Why are you sharing caches between customers?
Re:Ristretto: A High Performance, Concurrent, Memory-Bound G... by marktangotango on Saturday September 21, 2019 @09:47PM (#21039119)
Re:Ristretto: A High Performance, Concurrent, Memory-Bound G... by derekperkins on Saturday September 21, 2019 @12:01PM (#21036108)
Seems like you would just instantiate separate caches per customer if that's what you're looking for.
Re:Ristretto: A High Performance, Concurrent, Memory-Bound G... by hinkley on Saturday September 21, 2019 @07:19PM (#21038519)
Caches generally sit above the auth system. Sharing them between customers is a catastrophe waiting to happen.

We spend a lot of time here in postmortems asking what they hell were they thinking. This is a great opportunity to ask pre-catastrophe.