Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apache Geode: Distributed, in-memory database

geode.incubator.apache.org

Post reply on HN
Print view View original

61–65 of 65 posts

Re: Apache Geode: Distributed, in-memory database

#61

Post by rectang »

wmf wrote: post #49
orless wrote: post #26

Earlier quoted context omitted.

I wonder why Apache would need to have two "more similar than different" products.

Apache accepts anything that companies donate. (They say they don't, but it's hard to find anything they've rejected.)

That's not quite the right emphasis.

Apache is happy to provide a home for any community that is willing to adhere to our governance rules and traditions. Competing projects are OK.

Projects are almost never rejected because preparing a proposal for incubation is rigorous and many projects who would be a poor fit self-select out.

Source: former VP Apache Incubator, who has both helped prepare successful proposals and privately counseled projects who decided not to come to Apache.

Re: Apache Geode: Distributed, in-memory database

#62

Post by hyc_symas »

LoSboccacc wrote: post #57
hyc_symas wrote: post #44

Earlier quoted context omitted.

There's already memcacheDB for that https://github.com/LMDB/memcachedb

That one doesn't seem distributed. But I just glanced at the readme.

Distribution is usually handled by the memcache client libraries.

Re: Apache Geode: Distributed, in-memory database

#63

Post by mclarenfan »

LoSboccacc wrote: post #12

> Gemcached > Geode servers can be configured to talk memcached protocol. hey this is very interesting, it could work as a persistent acid memcached drop-in replacement!

Some advantages of gemcached over memcached are here:

https://cwiki.apache.org/confluence/display/GEODE/Moving+fro...

Re: Apache Geode: Distributed, in-memory database

#64

Post by krenoten »

jrallison wrote: post #43
krenoten wrote: post #33

Earlier quoted context omitted.

Redis is single-threaded, so everything it does on a per-node basis is implicitly atomic. You can also force the single thread to handle a block of commands from a single socket at once by using MULTI (otherwise commands can be interleaved with other commands from other sockets).

It's not guaranteed to be atomic in failure conditions. Also, the biggest difference between Redis and Geode would be the "distributed" part, which involves maintaining these guarantees across a cluster of machines (which Redis demonstratingly doesn't do).

That's pretty hand-wavey. All databases can be made to lose all guarantees under failure conditions.

Re: Apache Geode: Distributed, in-memory database

#65

Post by metatype »

wiradikusuma wrote: post #56

Sorry for the stupid question: how do in-memory DBs deal with power failures? e.g. someone walking in the server room and trip power cable. I can understand for read-only in-memory, but what about writes?

Also, geode supports redundancy zones so data is replicated such that a cluster can survive a rack failure without data loss.
Post reply on HN