Apache Geode: Distributed, in-memory database

Re:Apache Geode: Distributed, in-memory database by sandstrom on Thursday November 19, 2015 @03:25PM (#10597353)

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 for high availability and elastic scale.
    
    Holiday travel periods [Chinese New Year's] create peaks of 15,000 tickets 
    sold per minute, 1.4 billion page views per day and 40,000 visits per second.

http://pivotal.io/big-data/case-study/scaling-online-sales-f...

[ Parent | on HN ]

Re:Apache Geode: Distributed, in-memory database by trhway on Thursday November 19, 2015 @03:29PM (#10597386)

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

[ Parent | on HN ]

Re:Apache Geode: Distributed, in-memory database by GregChase on Thursday November 19, 2015 @03:45PM (#10597507)

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.

[ Parent | on HN ]

Re:Apache Geode: Distributed, in-memory database by trhway on Thursday November 19, 2015 @03:53PM (#10597575)

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

[ Parent | on HN ]

Re:Apache Geode: Distributed, in-memory database by sudsmenon on Thursday November 19, 2015 @03:49PM (#10597537)

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.

[ Parent | on HN ]

Re:Apache Geode: Distributed, in-memory database by mclarenfan on Thursday November 19, 2015 @03:38PM (#10597455)

Also Indian railways:

     200,000 Concurrent ticket Purchases

https://pivotal.io/big-data/case-study/distributed-in-memory...

[ Parent | on HN ]

Re:Apache Geode: Distributed, in-memory database by apache_rvs on Thursday November 19, 2015 @04:08PM (#10597675)

Geode wiki is quite good though: https://cwiki.apache.org/confluence/display/GEODE/Index

[ Parent | on HN ]