Andrew, The current github version is paralleled to GemFire 8.2 ?
Dor From: Eric Pederson [mailto:[email protected]] Sent: יום ו 29 ינואר 2016 02:36 To: [email protected] Subject: Re: Geode vs Gemfire? Geode is going to have continuous query? That's great! On Thursday, January 28, 2016, Gregory Chase <[email protected]<mailto:[email protected]>> wrote: I'm happy to take a stab here, wearing my Pivotal hat. On Thu, Jan 28, 2016 at 3:56 PM, Andrew Munn <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: What are the benefits of installing Geode vs Gemfire? What does Gemfire include that Geode does not? As soon as Apache Geode makes its release, which is coming soon, it will have much of what GemFire provides. Once the most recent code for WAN and continuous query are incorporated, Apache Geode will map even closer to GemFire. What's different is that Apache Geode is only supported here, in the forums. Releases will come on the schedule they come, and fixes will be incorporated, transparently, when they are completed in their own timeframe. With GemFire, you will have commercial support, which gives you the right to raise an SLA to get fixes and assistance. If, for example, you report a critical bug in GemFire, you will be issued a fix in a timely fashion. This fix, if it involves Apache Geode code, will eventually be contributed to the open source code, and incorporated as The Apache Way process allows. As time goes on, its likely that Apache Geode will spawn new features that GemFire will not adopt. As time goes on, its likely that GemFire will be more firmly meshed into Pivotal ecosystem components such as CloudFoundry, Spring, Greenplum, and other relevant technologies. The code for these integrate solutions will likely not be incorporated into Apache Geode. I hope this helps a bit. Thanks -- Greg Chase Director of Big Data Communities http://www.pivotal.io/big-data Pivotal Software http://www.pivotal.io/ 650-215-0477 @GregChase Blog: http://geekmarketing.biz/ -- Sent from Gmail Mobile This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp
