God: Scalable in Memory Data Structure Server in Go

Re:God: Scalable in Memory Data Structure Server in Go by rartichoke on Wednesday February 06, 2013 @08:39AM (#5176238)

I don't want to come off as a negative Nancy but why didn't you just stick to using Redis? What problems does your lib solve that Redis does not?

[ Parent | on HN ]

Re:God: Scalable in Memory Data Structure Server in Go by JulianMorrison on Friday February 08, 2013 @09:40AM (#5188046)

Distributed hash table algorithms were originally created for things like Gnutella and are optimal for cases where you expect nodes to pop up and disappear on a regular (but unpredictable) basis.

[ Parent | on HN ]

Re:God: Scalable in Memory Data Structure Server in Go by zond on Wednesday February 06, 2013 @05:27PM (#5179281)

If you run out of RAM or CPU on a single machine you start running into operationally problematic situations with Redis.

[ Parent | on HN ]

Re:God: Scalable in Memory Data Structure Server in Go by rartichoke on Wednesday February 06, 2013 @06:53PM (#5179698)

I've never had this issue pop up (I am not involved in any huge scale sites) but I have to believe this really isn't too common?

Also a 5 second Googling shows there's ways to set Redis up to stop writing but continue reading if you're running out of memory. If you really have that large memory needs then you're going to also run out of memory with this new lib on 1 machine.

It seems like Redis has more than enough options to prevent real problems from occurring once you do surpass your hardware requirements.

[ Parent | on HN ]

Re:God: Scalable in Memory Data Structure Server in Go by zond on Thursday February 07, 2013 @04:37AM (#5181250)

I guess it's not for you, then.

[ Parent | on HN ]