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

41–50 of 65 posts

Re: Apache Geode: Distributed, in-memory database

#41

Post by markito »

tuyguntn wrote: post #24

Landing page and documentation should be reconsidered. lots of unanswered questions, - distributed, in-memory database - how does it compare to SAP HANA? or Redis? if "... database" where is the querying language? if you have own querying language other than SQL please show us. - Performance is key - tell us about some benchmarks - Consistency is a must - CA or CP in CAP theorem? - Can I fully drop RDBMS in favor of…

Thanks for the feedback. We're currently updating the website and the work is being tracked here -> https://issues.apache.org/jira/browse/GEODE-53

Here is a quick preview of how the new one will look like: markito.github.io/geode-website/

Any feedback is welcome!

Re: Apache Geode: Distributed, in-memory database

#42

Post by fweespeech »

finnh wrote: post #30
tuyguntn wrote: post #24

Landing page and documentation should be reconsidered. lots of unanswered questions, - distributed, in-memory database - how does it compare to SAP HANA? or Redis? if "... database" where is the querying language? if you have own querying language other than SQL please show us. - Performance is key - tell us about some benchmarks - Consistency is a must - CA or CP in CAP theorem? - Can I fully drop RDBMS in favor of…

> - Consistency is a must - CA or CP in CAP theorem? There is no CA. So, they must mean CP. Remember, kids: if they promise CA, run away.

CA is possible if its read only, essentially, with all updates synchronized when a partition is not present [which is the majority of the time in the real world].

Re: Apache Geode: Distributed, in-memory database

#43

Post by jrallison »

krenoten wrote: post #33
glogla wrote: post #11

Earlier quoted context omitted.

This > Data is persisted in write-optimized disk storage. Consistency checking is configurable between highest performance caching and ACID transactions. seems pretty different to redis. I don't think Redis does ACID transactions.

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).

Re: Apache Geode: Distributed, in-memory database

#46

Post by espeed »

avodonosov wrote: post #36

Would you choose it over Datomic?

Datomic's immutable storage and time-travel query capabilities are awesome, and I often miss them in other DBs. But Datomic currently isn't designed for write-intensive workloads. And while you can shard Datomic's transactor and then combine multiple DBs in a query (http://nosql.mypopescu.com/post/19310504456/thoughts-about-d...), that's only going to get you so far.

However, Apache Geode lets you add custom indexes so it might not be too hard to add Clojure's persistent data structures as a custom index scheme and hook in Apache Geode as a backend to Clojure Datalog:

Clojure Datalog: https://github.com/fogus/bacwn

Datscript: https://github.com/tonsky/datascript

Clojure's Persistent Data Structures for Java: https://github.com/grignaak/clj-ds

Re: Apache Geode: Distributed, in-memory database

#47

Post by eloff »

fweespeech wrote: post #42
finnh wrote: post #30

Earlier quoted context omitted.

> - Consistency is a must - CA or CP in CAP theorem? There is no CA. So, they must mean CP. Remember, kids: if they promise CA, run away.

CA is possible if its read only, essentially, with all updates synchronized when a partition is not present [which is the majority of the time in the real world].

It's semantics, but I'd argue if you're read only than you're changing the definition of available.

Re: Apache Geode: Distributed, in-memory database

#48

Post by espeed »

Two Videos:

1. "Open Sourced GemFire In-Memory Distributed Database and Apache Contributors" (https://www.youtube.com/playlist?list=PL62pIycqXx-TTMXsq09BE...)

2. "Creating a Highly Scalable Stock Prediction System with R, Geode & Spring XD" (https://www.youtube.com/playlist?list=PL62pIycqXx-Rzd_HcjU7Y...)

Re: Apache Geode: Distributed, in-memory database

#49

Post by wmf »

orless wrote: post #26
GregChase wrote: post #21

Earlier quoted context omitted.

Apache Geode and Apache Ignite are more similar than they are different. Apache Ignite, based off the commercial distribution Grid Gain is newer to market. Apache Geode, based off the commercial distribution GemFire, has a long history in the market.

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.)

Re: Apache Geode: Distributed, in-memory database

#50

Post by jacques_chester »

FWIW, Pivotal is hiring in our Big Data team, largely based in Palo Alto. Geode (incubating), HAWQ (incubating), Greenplum, Pivotal HD, MADlib etc are all mostly developed with engineering effort that we donate.

Hit me up with an email (jchester@pivotal.io) or visit pivotal.io/careers if you're interested.

Post reply on HN