Live data from Hacker News

Apache Geode: Distributed, in-memory database

geode.incubator.apache.org

21–30 of 65 posts

Re: Apache Geode: Distributed, in-memory database

#21
post #19

I'm starting to get lost in the new Apache animals. How does Apache Goede compares to Apache Ignite (advertised as "in-memory data fabric"?

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.

Re: Apache Geode: Distributed, in-memory database

#23
post #16

Didn't understand much from the linked page, but I found this website (from Pivotal, the commercial entity behind Geode) quite informative. Perhaps it's useful to others. https://pivotal.io/big-data/pivotal-gemfire === I found this interesting deployment: China National Railways use Geode to run railway ticketing for the entire country with a 10 node cluster, managing 2 TB of "hot data" in memory, and 10 backup nodes…

to understand where it comes historically and ideologically/architecturally from - the keyword here is Smalltalk https://en.wikipedia.org/wiki/Gemstone_%28database%29 The guys have been for 3 decades sitting on the forested Oregon river bank (the place is called Beavertown for reason :) thinking straight and clear in Smalltalk... :)

Geode and its predecessor GemFire are pure Java.

The original engineering expertise came from the team that built the Gemstone OODB.

Beaverton isn't so forested anymore, but lots of indigenous object oriented expertise for sure.

Re: Apache Geode: Distributed, in-memory database

#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 Geode?

- web site built as Landing page/PR for product, then all of a sudden starts Community/Contributors/Getting started columns, with loooooong list of mailing lists, smaller content for contributors and very important part(getting started) presented as tiny small link :(, please put there some useful info about product, you already have Community/Contribute menus.

Re: Apache Geode: Distributed, in-memory database

#25
post #16

Didn't understand much from the linked page, but I found this website (from Pivotal, the commercial entity behind Geode) quite informative. Perhaps it's useful to others. https://pivotal.io/big-data/pivotal-gemfire === I found this interesting deployment: China National Railways use Geode to run railway ticketing for the entire country with a 10 node cluster, managing 2 TB of "hot data" in memory, and 10 backup nodes…

to understand where it comes historically and ideologically/architecturally from - the keyword here is Smalltalk https://en.wikipedia.org/wiki/Gemstone_%28database%29 The guys have been for 3 decades sitting on the forested Oregon river bank (the place is called Beavertown for reason :) thinking straight and clear in Smalltalk... :)

FWIW, GemFire is all written in Java and has native clients for c++ and .net ( as well as REST clients). The product was built from the ground up in Java and runs highly scaled up , low latency systems across the globe. The place is called Beaverton and while there are many beautiful forested riverbanks, the Pivotal team does not sit next to one.

Re: Apache Geode: Distributed, in-memory database

#26
post #19

I'm starting to get lost in the new Apache animals. How does Apache Goede compares to Apache Ignite (advertised as "in-memory data fabric"?

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.

Re: Apache Geode: Distributed, in-memory database

#27
post #19

I'm starting to get lost in the new Apache animals. How does Apache Goede compares to Apache Ignite (advertised as "in-memory data fabric"?

Ignite vs Pivotal Gemfilre (Apache Geode) https://ignite.apache.org/use-cases/compare/gemfire.html

This is cool: "Ignite allows for most of the data structures from java.util.concurrent framework to be used in a distributed fashion." https://ignite.apache.org/features/datastructures.html

Re: Apache Geode: Distributed, in-memory database

#28
post #16

Earlier quoted context omitted.

to understand where it comes historically and ideologically/architecturally from - the keyword here is Smalltalk https://en.wikipedia.org/wiki/Gemstone_%28database%29 The guys have been for 3 decades sitting on the forested Oregon river bank (the place is called Beavertown for reason :) thinking straight and clear in Smalltalk... :)

Geode and its predecessor GemFire are pure Java. The original engineering expertise came from the team that built the Gemstone OODB. Beaverton isn't so forested anymore, but lots of indigenous object oriented expertise for sure.

>Geode and its predecessor GemFire are pure Java.

i know (was talking at some point about joining, already here in SV), and this is why i wrote only "3 decades" as i don't know precise dates of GemFire only suppose it to be beginning of 200x. My simple arithmetics mistake though - 2002 - 1982 is 2 decades, sorry, i see where confusion comes from :)

Re: Apache Geode: Distributed, in-memory database

#29

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…

Complex objects can be stored by key and automatically partitioned and replicated. Query the data with OQL (an ODMG standard). For example:

select * from /person p where p.name = 'foo' and p.age > 42

Re: Apache Geode: Distributed, in-memory database

#30

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.

Post reply on HN