You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Greg Chase <gr...@gregchase.com> on 2015/09/15 01:44:08 UTC
Apache Geode is....
Dear Geode contributors,
I'm writing the website for the newly accepted Apache HAWQ incubating
project.
As part of this effort, I secured some web design resources to refresh the
Apache Geode site as well.
Talking to a number of contributors individually, they like the idea of
changing the design somewhat to fit the CouchDB layout:
http://couchdb.apache.org/, but keeping the 'Geode' graphics and look and
feel.
Its also a good time to refresh our general text which hasn't really been
updated since before Geode joined Apache.
First panel is a short description explaining what Geode is:
"Apache Geode is a distributed, in-memory data grid and integrated
messaging queue built to support low latency transactional applications at
extreme scale."
Should be 25 words or less. 20 words or less is even better. My score is
"22".
Re: Apache Geode is....
Posted by Greg Chase <gr...@gregchase.com>.
Second frame is "About Apache Geode". 150 words or less for the body. I'm
10 over at 160.
What we currently say right now needs a total rewrite:
http://geode.incubator.apache.org/about/
Proposed new About text (150 words or less for the body. I'm 10 over at
160):
Processing low latency queries, transactions, and event messaging at high
concurrency
Apache Geode (incubating) was first developed to solve performance issues
at scale for commodities traders after the crash of Enron in 2002. It was
released to the market as the commercial product GemFire, a product of
Gemstone Systems. In April 2015, The code was granted to The ASF as Apache
Geode (incubating).
Apache Geode is a distributed in-memory database and integrated event
message queue built with three design principles:
1.
Elastic performance: Maintain low latency response through a
self-balancing cluster architecture while keeping all data in-memory
2.
Distributed consistency: Guarantee consistency of data across
distributed nodes of a cluster to support ACID transactions
3.
Resilient availability: Without sacrificing consistency, ensure data
remains available in a cluster through automated, redundancy, rebalancing,
and self healing of the cluster
Geode nodes have an integrated message queue for delivering administrative
and cache events. Events can match queries, be synchronous or
asynchronous, are ordered, persistent, and highly available. This
implements powerful capabilities such as guaranteed write-behind to RDBMS.
On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com> wrote:
> Dear Geode contributors,
> I'm writing the website for the newly accepted Apache HAWQ incubating
> project.
>
> As part of this effort, I secured some web design resources to refresh the
> Apache Geode site as well.
>
> Talking to a number of contributors individually, they like the idea of
> changing the design somewhat to fit the CouchDB layout:
> http://couchdb.apache.org/, but keeping the 'Geode' graphics and look and
> feel.
>
> Its also a good time to refresh our general text which hasn't really been
> updated since before Geode joined Apache.
>
> First panel is a short description explaining what Geode is:
>
> "Apache Geode is a distributed, in-memory data grid and integrated
> messaging queue built to support low latency transactional applications at
> extreme scale."
>
> Should be 25 words or less. 20 words or less is even better. My score is
> "22".
>
Re: Apache Geode is....
Posted by Gregory Chase <gc...@pivotal.io>.
Now you know why marketing people have their jobs :)
I still think "Event message queue" is the best three word description for
this group of features.
Just so you know, the prior version of this statement doesn't even mention
the "event message queue", but its a key feature, so wanted to elevate it
in the main description.
On Tue, Sep 15, 2015 at 11:17 AM, Michael Stolz <ms...@pivotal.io> wrote:
> Hard to keep it down to so few words. I'd love to have "parallel,
> persistent, guaranteed eventing system" but its too many words.
>
> --
> Mike Stolz
> Principal Technical Account Manager
> Mobile: 631-835-4771
>
> On Tue, Sep 15, 2015 at 11:14 AM, Gregory Chase <gc...@pivotal.io> wrote:
>
> > Please recommend some different language to "event message queue".
> > "Eventing system" lacks some detail and highlighting some wonderful
> > capabilities of Geode in persistence, guaranteed delivery, and parallel
> > operation. "Eventing system" does imply callbacks and hooks like what
> Geode
> > has. However I'm hoping "Event message queue" implies that as well since
> > this isn't just something like "RabbitMQ" pasted onto the database nodes
> :)
> >
> > -Greg
> >
> > On Tue, Sep 15, 2015 at 11:10 AM, Michael Stolz <ms...@pivotal.io>
> wrote:
> >
> > > I'm not real happy with the "messaging queue" terminology. I prefer to
> > > think of it as an "eventing system". Messaging queues have a lot of
> > > connotations associated with them that really aren't the way our
> eventing
> > > mechanism works.
> > >
> > > --
> > > Mike Stolz
> > > Principal Technical Account Manager
> > > Mobile: 631-835-4771
> > >
> > > On Tue, Sep 15, 2015 at 10:33 AM, Gregory Chase <gc...@pivotal.io>
> > wrote:
> > >
> > > > I was trying to cover "high concurrency" in the "extreme scale"
> bucket,
> > > but
> > > > I would agree that being precise about scale is better. Geode deals
> in
> > > > in-memory terabytes, not Petabytes at rest.
> > > >
> > > > Taking your feedback Ashvin, we can get tighter:
> > > >
> > > > Apache Geode is a distributed, in-memory data grid and
> > > > integrated messaging queue built to support
> > > > low latency transactional applications
> > > > at very high concurrency.
> > > >
> > > > On Tue, Sep 15, 2015 at 10:30 AM, Ashvin A <aa...@gmail.com>
> wrote:
> > > >
> > > > > Hi Greg,
> > > > >
> > > > > I pretty much like the short description you provided. I would like
> > to
> > > > add
> > > > > "high concurrency" in the mix for completeness. Which would make it
> > > > (22+2)
> > > > > < 25 words.
> > > > >
> > > > > Apache Geode is a distributed, in-memory data grid and
> > > > > integrated messaging queue built to support
> > > > > low latency *high concurrency* transactional applications
> > > > > at extreme scale
> > > > >
> > > > > $ 0.01
> > > > >
> > > > > -ashvin
> > > > >
> > > > > On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com>
> > > wrote:
> > > > >
> > > > > > Dear Geode contributors,
> > > > > > I'm writing the website for the newly accepted Apache HAWQ
> > incubating
> > > > > > project.
> > > > > >
> > > > > > As part of this effort, I secured some web design resources to
> > > refresh
> > > > > the
> > > > > > Apache Geode site as well.
> > > > > >
> > > > > > Talking to a number of contributors individually, they like the
> > idea
> > > of
> > > > > > changing the design somewhat to fit the CouchDB layout:
> > > > > > http://couchdb.apache.org/, but keeping the 'Geode' graphics and
> > > look
> > > > > and
> > > > > > feel.
> > > > > >
> > > > > > Its also a good time to refresh our general text which hasn't
> > really
> > > > been
> > > > > > updated since before Geode joined Apache.
> > > > > >
> > > > > > First panel is a short description explaining what Geode is:
> > > > > >
> > > > > > "Apache Geode is a distributed, in-memory data grid and
> integrated
> > > > > > messaging queue built to support low latency transactional
> > > applications
> > > > > at
> > > > > > extreme scale."
> > > > > >
> > > > > > Should be 25 words or less. 20 words or less is even better. My
> > score
> > > > is
> > > > > > "22".
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > 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/
> > > >
> > >
> >
> >
> >
> > --
> > 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/
> >
>
--
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/
Re: Apache Geode is....
Posted by Michael Stolz <ms...@pivotal.io>.
Hard to keep it down to so few words. I'd love to have "parallel,
persistent, guaranteed eventing system" but its too many words.
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Tue, Sep 15, 2015 at 11:14 AM, Gregory Chase <gc...@pivotal.io> wrote:
> Please recommend some different language to "event message queue".
> "Eventing system" lacks some detail and highlighting some wonderful
> capabilities of Geode in persistence, guaranteed delivery, and parallel
> operation. "Eventing system" does imply callbacks and hooks like what Geode
> has. However I'm hoping "Event message queue" implies that as well since
> this isn't just something like "RabbitMQ" pasted onto the database nodes :)
>
> -Greg
>
> On Tue, Sep 15, 2015 at 11:10 AM, Michael Stolz <ms...@pivotal.io> wrote:
>
> > I'm not real happy with the "messaging queue" terminology. I prefer to
> > think of it as an "eventing system". Messaging queues have a lot of
> > connotations associated with them that really aren't the way our eventing
> > mechanism works.
> >
> > --
> > Mike Stolz
> > Principal Technical Account Manager
> > Mobile: 631-835-4771
> >
> > On Tue, Sep 15, 2015 at 10:33 AM, Gregory Chase <gc...@pivotal.io>
> wrote:
> >
> > > I was trying to cover "high concurrency" in the "extreme scale" bucket,
> > but
> > > I would agree that being precise about scale is better. Geode deals in
> > > in-memory terabytes, not Petabytes at rest.
> > >
> > > Taking your feedback Ashvin, we can get tighter:
> > >
> > > Apache Geode is a distributed, in-memory data grid and
> > > integrated messaging queue built to support
> > > low latency transactional applications
> > > at very high concurrency.
> > >
> > > On Tue, Sep 15, 2015 at 10:30 AM, Ashvin A <aa...@gmail.com> wrote:
> > >
> > > > Hi Greg,
> > > >
> > > > I pretty much like the short description you provided. I would like
> to
> > > add
> > > > "high concurrency" in the mix for completeness. Which would make it
> > > (22+2)
> > > > < 25 words.
> > > >
> > > > Apache Geode is a distributed, in-memory data grid and
> > > > integrated messaging queue built to support
> > > > low latency *high concurrency* transactional applications
> > > > at extreme scale
> > > >
> > > > $ 0.01
> > > >
> > > > -ashvin
> > > >
> > > > On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com>
> > wrote:
> > > >
> > > > > Dear Geode contributors,
> > > > > I'm writing the website for the newly accepted Apache HAWQ
> incubating
> > > > > project.
> > > > >
> > > > > As part of this effort, I secured some web design resources to
> > refresh
> > > > the
> > > > > Apache Geode site as well.
> > > > >
> > > > > Talking to a number of contributors individually, they like the
> idea
> > of
> > > > > changing the design somewhat to fit the CouchDB layout:
> > > > > http://couchdb.apache.org/, but keeping the 'Geode' graphics and
> > look
> > > > and
> > > > > feel.
> > > > >
> > > > > Its also a good time to refresh our general text which hasn't
> really
> > > been
> > > > > updated since before Geode joined Apache.
> > > > >
> > > > > First panel is a short description explaining what Geode is:
> > > > >
> > > > > "Apache Geode is a distributed, in-memory data grid and integrated
> > > > > messaging queue built to support low latency transactional
> > applications
> > > > at
> > > > > extreme scale."
> > > > >
> > > > > Should be 25 words or less. 20 words or less is even better. My
> score
> > > is
> > > > > "22".
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > 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/
> > >
> >
>
>
>
> --
> 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/
>
Re: Apache Geode is....
Posted by Gregory Chase <gc...@pivotal.io>.
Please recommend some different language to "event message queue".
"Eventing system" lacks some detail and highlighting some wonderful
capabilities of Geode in persistence, guaranteed delivery, and parallel
operation. "Eventing system" does imply callbacks and hooks like what Geode
has. However I'm hoping "Event message queue" implies that as well since
this isn't just something like "RabbitMQ" pasted onto the database nodes :)
-Greg
On Tue, Sep 15, 2015 at 11:10 AM, Michael Stolz <ms...@pivotal.io> wrote:
> I'm not real happy with the "messaging queue" terminology. I prefer to
> think of it as an "eventing system". Messaging queues have a lot of
> connotations associated with them that really aren't the way our eventing
> mechanism works.
>
> --
> Mike Stolz
> Principal Technical Account Manager
> Mobile: 631-835-4771
>
> On Tue, Sep 15, 2015 at 10:33 AM, Gregory Chase <gc...@pivotal.io> wrote:
>
> > I was trying to cover "high concurrency" in the "extreme scale" bucket,
> but
> > I would agree that being precise about scale is better. Geode deals in
> > in-memory terabytes, not Petabytes at rest.
> >
> > Taking your feedback Ashvin, we can get tighter:
> >
> > Apache Geode is a distributed, in-memory data grid and
> > integrated messaging queue built to support
> > low latency transactional applications
> > at very high concurrency.
> >
> > On Tue, Sep 15, 2015 at 10:30 AM, Ashvin A <aa...@gmail.com> wrote:
> >
> > > Hi Greg,
> > >
> > > I pretty much like the short description you provided. I would like to
> > add
> > > "high concurrency" in the mix for completeness. Which would make it
> > (22+2)
> > > < 25 words.
> > >
> > > Apache Geode is a distributed, in-memory data grid and
> > > integrated messaging queue built to support
> > > low latency *high concurrency* transactional applications
> > > at extreme scale
> > >
> > > $ 0.01
> > >
> > > -ashvin
> > >
> > > On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com>
> wrote:
> > >
> > > > Dear Geode contributors,
> > > > I'm writing the website for the newly accepted Apache HAWQ incubating
> > > > project.
> > > >
> > > > As part of this effort, I secured some web design resources to
> refresh
> > > the
> > > > Apache Geode site as well.
> > > >
> > > > Talking to a number of contributors individually, they like the idea
> of
> > > > changing the design somewhat to fit the CouchDB layout:
> > > > http://couchdb.apache.org/, but keeping the 'Geode' graphics and
> look
> > > and
> > > > feel.
> > > >
> > > > Its also a good time to refresh our general text which hasn't really
> > been
> > > > updated since before Geode joined Apache.
> > > >
> > > > First panel is a short description explaining what Geode is:
> > > >
> > > > "Apache Geode is a distributed, in-memory data grid and integrated
> > > > messaging queue built to support low latency transactional
> applications
> > > at
> > > > extreme scale."
> > > >
> > > > Should be 25 words or less. 20 words or less is even better. My score
> > is
> > > > "22".
> > > >
> > >
> >
> >
> >
> > --
> > 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/
> >
>
--
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/
Re: Apache Geode is....
Posted by John Blum <jb...@pivotal.io>.
At SpringOne, I used the following definition during Luke and I's talk
which seemed to resonate with people...
A distributed, in-memory compute and data management platform that elastically
scales to achieve high-throughput, low-latency access to big, fast
data powering
business critical, analytical applications in real-time.
You could include, "high-throughput, low-latency and consistent access
to...". Use either "Grid" or "Distributed", not both since one implies the
other.
I don't find "(Event) Messaging Queue" all that useful in describing Gem
since Gem is not a traditional pub/sub system with topics and "API"
supporting that programming model, which is essential to messaging. More
importantly, a "queue" is not a first class citizen in Gem; you need a
Region to create any kind of queue (e.g. AEQ), and, while a Region could be
designated as a kind of "topic" based queue to dump messages, people don't
think of it that way. Also, you need to use a client/server architecture
to achieve "subscription" like capabilities with RI and CQs. Callbacks
with Listeners are not the same thing as subscription and not asynchronous
without the use of AEQs and Listeners. In short, the "messaging" story is
complete at best.
In general, the adjectives describing Gem are to numerous to enumerate in a
"definition". See here
<http://www.slideshare.net/john_blum/clipboards/my-clips> for example, and
event this list is incomplete because I don't mention transactional, for
instance.
On Tue, Sep 15, 2015 at 11:24 AM, Gregory Chase <gc...@pivotal.io> wrote:
> Anthony, can you please suggest what the wording of the statement should
> be:
>
> > Apache Geode is a distributed, in-memory data grid and
> >> integrated messaging queue built to support
> >> low latency transactional applications
> >> at very high concurrency.
>
> I used "transactional" to imply the need for ACID.
>
> We call the commercial distribution at Pivotal a "database" to imply
> support for ACID transactions. However, for Apache Geode, I think its
> important to clearly define the technological architecture. Geode is a
> data grid that can operate as a database - how cool is that?
>
>
> On Tue, Sep 15, 2015 at 11:19 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> > Yea, I was thinking along those lines as well Mike.
> >
> > Also “strong consistency” as opposed to eventual, etc regarding data
> loss.
> >
> > Anthony
> >
> > > On Sep 15, 2015, at 11:10 AM, Michael Stolz <ms...@pivotal.io> wrote:
> > >
> > > I'm not real happy with the "messaging queue" terminology. I prefer to
> > > think of it as an "eventing system". Messaging queues have a lot of
> > > connotations associated with them that really aren't the way our
> eventing
> > > mechanism works.
> > >
> > > --
> > > Mike Stolz
> > > Principal Technical Account Manager
> > > Mobile: 631-835-4771
> > >
> > > On Tue, Sep 15, 2015 at 10:33 AM, Gregory Chase <gc...@pivotal.io>
> > wrote:
> > >
> > >> I was trying to cover "high concurrency" in the "extreme scale"
> bucket,
> > but
> > >> I would agree that being precise about scale is better. Geode deals
> in
> > >> in-memory terabytes, not Petabytes at rest.
> > >>
> > >> Taking your feedback Ashvin, we can get tighter:
> > >>
> > >> Apache Geode is a distributed, in-memory data grid and
> > >> integrated messaging queue built to support
> > >> low latency transactional applications
> > >> at very high concurrency.
> > >>
> > >> On Tue, Sep 15, 2015 at 10:30 AM, Ashvin A <aa...@gmail.com> wrote:
> > >>
> > >>> Hi Greg,
> > >>>
> > >>> I pretty much like the short description you provided. I would like
> to
> > >> add
> > >>> "high concurrency" in the mix for completeness. Which would make it
> > >> (22+2)
> > >>> < 25 words.
> > >>>
> > >>> Apache Geode is a distributed, in-memory data grid and
> > >>> integrated messaging queue built to support
> > >>> low latency *high concurrency* transactional applications
> > >>> at extreme scale
> > >>>
> > >>> $ 0.01
> > >>>
> > >>> -ashvin
> > >>>
> > >>> On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com>
> > wrote:
> > >>>
> > >>>> Dear Geode contributors,
> > >>>> I'm writing the website for the newly accepted Apache HAWQ
> incubating
> > >>>> project.
> > >>>>
> > >>>> As part of this effort, I secured some web design resources to
> refresh
> > >>> the
> > >>>> Apache Geode site as well.
> > >>>>
> > >>>> Talking to a number of contributors individually, they like the idea
> > of
> > >>>> changing the design somewhat to fit the CouchDB layout:
> > >>>> http://couchdb.apache.org/, but keeping the 'Geode' graphics and
> look
> > >>> and
> > >>>> feel.
> > >>>>
> > >>>> Its also a good time to refresh our general text which hasn't really
> > >> been
> > >>>> updated since before Geode joined Apache.
> > >>>>
> > >>>> First panel is a short description explaining what Geode is:
> > >>>>
> > >>>> "Apache Geode is a distributed, in-memory data grid and integrated
> > >>>> messaging queue built to support low latency transactional
> > applications
> > >>> at
> > >>>> extreme scale."
> > >>>>
> > >>>> Should be 25 words or less. 20 words or less is even better. My
> score
> > >> is
> > >>>> "22".
> > >>>>
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> 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/
> > >>
> >
> >
>
>
> --
> 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/
>
--
-John
503-504-8657
john.blum10101 (skype)
Re: Apache Geode is....
Posted by Gregory Chase <gc...@pivotal.io>.
Anthony, can you please suggest what the wording of the statement should
be:
> Apache Geode is a distributed, in-memory data grid and
>> integrated messaging queue built to support
>> low latency transactional applications
>> at very high concurrency.
I used "transactional" to imply the need for ACID.
We call the commercial distribution at Pivotal a "database" to imply
support for ACID transactions. However, for Apache Geode, I think its
important to clearly define the technological architecture. Geode is a
data grid that can operate as a database - how cool is that?
On Tue, Sep 15, 2015 at 11:19 AM, Anthony Baker <ab...@pivotal.io> wrote:
> Yea, I was thinking along those lines as well Mike.
>
> Also “strong consistency” as opposed to eventual, etc regarding data loss.
>
> Anthony
>
> > On Sep 15, 2015, at 11:10 AM, Michael Stolz <ms...@pivotal.io> wrote:
> >
> > I'm not real happy with the "messaging queue" terminology. I prefer to
> > think of it as an "eventing system". Messaging queues have a lot of
> > connotations associated with them that really aren't the way our eventing
> > mechanism works.
> >
> > --
> > Mike Stolz
> > Principal Technical Account Manager
> > Mobile: 631-835-4771
> >
> > On Tue, Sep 15, 2015 at 10:33 AM, Gregory Chase <gc...@pivotal.io>
> wrote:
> >
> >> I was trying to cover "high concurrency" in the "extreme scale" bucket,
> but
> >> I would agree that being precise about scale is better. Geode deals in
> >> in-memory terabytes, not Petabytes at rest.
> >>
> >> Taking your feedback Ashvin, we can get tighter:
> >>
> >> Apache Geode is a distributed, in-memory data grid and
> >> integrated messaging queue built to support
> >> low latency transactional applications
> >> at very high concurrency.
> >>
> >> On Tue, Sep 15, 2015 at 10:30 AM, Ashvin A <aa...@gmail.com> wrote:
> >>
> >>> Hi Greg,
> >>>
> >>> I pretty much like the short description you provided. I would like to
> >> add
> >>> "high concurrency" in the mix for completeness. Which would make it
> >> (22+2)
> >>> < 25 words.
> >>>
> >>> Apache Geode is a distributed, in-memory data grid and
> >>> integrated messaging queue built to support
> >>> low latency *high concurrency* transactional applications
> >>> at extreme scale
> >>>
> >>> $ 0.01
> >>>
> >>> -ashvin
> >>>
> >>> On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com>
> wrote:
> >>>
> >>>> Dear Geode contributors,
> >>>> I'm writing the website for the newly accepted Apache HAWQ incubating
> >>>> project.
> >>>>
> >>>> As part of this effort, I secured some web design resources to refresh
> >>> the
> >>>> Apache Geode site as well.
> >>>>
> >>>> Talking to a number of contributors individually, they like the idea
> of
> >>>> changing the design somewhat to fit the CouchDB layout:
> >>>> http://couchdb.apache.org/, but keeping the 'Geode' graphics and look
> >>> and
> >>>> feel.
> >>>>
> >>>> Its also a good time to refresh our general text which hasn't really
> >> been
> >>>> updated since before Geode joined Apache.
> >>>>
> >>>> First panel is a short description explaining what Geode is:
> >>>>
> >>>> "Apache Geode is a distributed, in-memory data grid and integrated
> >>>> messaging queue built to support low latency transactional
> applications
> >>> at
> >>>> extreme scale."
> >>>>
> >>>> Should be 25 words or less. 20 words or less is even better. My score
> >> is
> >>>> "22".
> >>>>
> >>>
> >>
> >>
> >>
> >> --
> >> 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/
> >>
>
>
--
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/
Re: Apache Geode is....
Posted by Anthony Baker <ab...@pivotal.io>.
Yea, I was thinking along those lines as well Mike.
Also “strong consistency” as opposed to eventual, etc regarding data loss.
Anthony
> On Sep 15, 2015, at 11:10 AM, Michael Stolz <ms...@pivotal.io> wrote:
>
> I'm not real happy with the "messaging queue" terminology. I prefer to
> think of it as an "eventing system". Messaging queues have a lot of
> connotations associated with them that really aren't the way our eventing
> mechanism works.
>
> --
> Mike Stolz
> Principal Technical Account Manager
> Mobile: 631-835-4771
>
> On Tue, Sep 15, 2015 at 10:33 AM, Gregory Chase <gc...@pivotal.io> wrote:
>
>> I was trying to cover "high concurrency" in the "extreme scale" bucket, but
>> I would agree that being precise about scale is better. Geode deals in
>> in-memory terabytes, not Petabytes at rest.
>>
>> Taking your feedback Ashvin, we can get tighter:
>>
>> Apache Geode is a distributed, in-memory data grid and
>> integrated messaging queue built to support
>> low latency transactional applications
>> at very high concurrency.
>>
>> On Tue, Sep 15, 2015 at 10:30 AM, Ashvin A <aa...@gmail.com> wrote:
>>
>>> Hi Greg,
>>>
>>> I pretty much like the short description you provided. I would like to
>> add
>>> "high concurrency" in the mix for completeness. Which would make it
>> (22+2)
>>> < 25 words.
>>>
>>> Apache Geode is a distributed, in-memory data grid and
>>> integrated messaging queue built to support
>>> low latency *high concurrency* transactional applications
>>> at extreme scale
>>>
>>> $ 0.01
>>>
>>> -ashvin
>>>
>>> On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com> wrote:
>>>
>>>> Dear Geode contributors,
>>>> I'm writing the website for the newly accepted Apache HAWQ incubating
>>>> project.
>>>>
>>>> As part of this effort, I secured some web design resources to refresh
>>> the
>>>> Apache Geode site as well.
>>>>
>>>> Talking to a number of contributors individually, they like the idea of
>>>> changing the design somewhat to fit the CouchDB layout:
>>>> http://couchdb.apache.org/, but keeping the 'Geode' graphics and look
>>> and
>>>> feel.
>>>>
>>>> Its also a good time to refresh our general text which hasn't really
>> been
>>>> updated since before Geode joined Apache.
>>>>
>>>> First panel is a short description explaining what Geode is:
>>>>
>>>> "Apache Geode is a distributed, in-memory data grid and integrated
>>>> messaging queue built to support low latency transactional applications
>>> at
>>>> extreme scale."
>>>>
>>>> Should be 25 words or less. 20 words or less is even better. My score
>> is
>>>> "22".
>>>>
>>>
>>
>>
>>
>> --
>> 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/
>>
Re: Apache Geode is....
Posted by Michael Stolz <ms...@pivotal.io>.
I'm not real happy with the "messaging queue" terminology. I prefer to
think of it as an "eventing system". Messaging queues have a lot of
connotations associated with them that really aren't the way our eventing
mechanism works.
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Tue, Sep 15, 2015 at 10:33 AM, Gregory Chase <gc...@pivotal.io> wrote:
> I was trying to cover "high concurrency" in the "extreme scale" bucket, but
> I would agree that being precise about scale is better. Geode deals in
> in-memory terabytes, not Petabytes at rest.
>
> Taking your feedback Ashvin, we can get tighter:
>
> Apache Geode is a distributed, in-memory data grid and
> integrated messaging queue built to support
> low latency transactional applications
> at very high concurrency.
>
> On Tue, Sep 15, 2015 at 10:30 AM, Ashvin A <aa...@gmail.com> wrote:
>
> > Hi Greg,
> >
> > I pretty much like the short description you provided. I would like to
> add
> > "high concurrency" in the mix for completeness. Which would make it
> (22+2)
> > < 25 words.
> >
> > Apache Geode is a distributed, in-memory data grid and
> > integrated messaging queue built to support
> > low latency *high concurrency* transactional applications
> > at extreme scale
> >
> > $ 0.01
> >
> > -ashvin
> >
> > On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com> wrote:
> >
> > > Dear Geode contributors,
> > > I'm writing the website for the newly accepted Apache HAWQ incubating
> > > project.
> > >
> > > As part of this effort, I secured some web design resources to refresh
> > the
> > > Apache Geode site as well.
> > >
> > > Talking to a number of contributors individually, they like the idea of
> > > changing the design somewhat to fit the CouchDB layout:
> > > http://couchdb.apache.org/, but keeping the 'Geode' graphics and look
> > and
> > > feel.
> > >
> > > Its also a good time to refresh our general text which hasn't really
> been
> > > updated since before Geode joined Apache.
> > >
> > > First panel is a short description explaining what Geode is:
> > >
> > > "Apache Geode is a distributed, in-memory data grid and integrated
> > > messaging queue built to support low latency transactional applications
> > at
> > > extreme scale."
> > >
> > > Should be 25 words or less. 20 words or less is even better. My score
> is
> > > "22".
> > >
> >
>
>
>
> --
> 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/
>
Re: Apache Geode is....
Posted by Gregory Chase <gc...@pivotal.io>.
I was trying to cover "high concurrency" in the "extreme scale" bucket, but
I would agree that being precise about scale is better. Geode deals in
in-memory terabytes, not Petabytes at rest.
Taking your feedback Ashvin, we can get tighter:
Apache Geode is a distributed, in-memory data grid and
integrated messaging queue built to support
low latency transactional applications
at very high concurrency.
On Tue, Sep 15, 2015 at 10:30 AM, Ashvin A <aa...@gmail.com> wrote:
> Hi Greg,
>
> I pretty much like the short description you provided. I would like to add
> "high concurrency" in the mix for completeness. Which would make it (22+2)
> < 25 words.
>
> Apache Geode is a distributed, in-memory data grid and
> integrated messaging queue built to support
> low latency *high concurrency* transactional applications
> at extreme scale
>
> $ 0.01
>
> -ashvin
>
> On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com> wrote:
>
> > Dear Geode contributors,
> > I'm writing the website for the newly accepted Apache HAWQ incubating
> > project.
> >
> > As part of this effort, I secured some web design resources to refresh
> the
> > Apache Geode site as well.
> >
> > Talking to a number of contributors individually, they like the idea of
> > changing the design somewhat to fit the CouchDB layout:
> > http://couchdb.apache.org/, but keeping the 'Geode' graphics and look
> and
> > feel.
> >
> > Its also a good time to refresh our general text which hasn't really been
> > updated since before Geode joined Apache.
> >
> > First panel is a short description explaining what Geode is:
> >
> > "Apache Geode is a distributed, in-memory data grid and integrated
> > messaging queue built to support low latency transactional applications
> at
> > extreme scale."
> >
> > Should be 25 words or less. 20 words or less is even better. My score is
> > "22".
> >
>
--
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/
Re: Apache Geode is....
Posted by Ashvin A <aa...@gmail.com>.
Hi Greg,
I pretty much like the short description you provided. I would like to add
"high concurrency" in the mix for completeness. Which would make it (22+2)
< 25 words.
Apache Geode is a distributed, in-memory data grid and
integrated messaging queue built to support
low latency *high concurrency* transactional applications
at extreme scale
$ 0.01
-ashvin
On Mon, Sep 14, 2015 at 4:44 PM, Greg Chase <gr...@gregchase.com> wrote:
> Dear Geode contributors,
> I'm writing the website for the newly accepted Apache HAWQ incubating
> project.
>
> As part of this effort, I secured some web design resources to refresh the
> Apache Geode site as well.
>
> Talking to a number of contributors individually, they like the idea of
> changing the design somewhat to fit the CouchDB layout:
> http://couchdb.apache.org/, but keeping the 'Geode' graphics and look and
> feel.
>
> Its also a good time to refresh our general text which hasn't really been
> updated since before Geode joined Apache.
>
> First panel is a short description explaining what Geode is:
>
> "Apache Geode is a distributed, in-memory data grid and integrated
> messaging queue built to support low latency transactional applications at
> extreme scale."
>
> Should be 25 words or less. 20 words or less is even better. My score is
> "22".
>
Re: Apache Geode is....
Posted by Gregory Chase <gc...@pivotal.io>.
On Fri, Sep 18, 2015 at 12:46 PM, Sai Boorlagadda <sb...@pivotal.io>
wrote:
> As a newbie, I suggest to change the order of the “adjectives of gemfire”
> to keep "in-memory database" to-gether.
>
> Apache Geode is a highly distributed, strongly consistent, in-memory
> database built to support low-latency transactional applications.
>
> Don’t know if it makes any difference? all I know is gemfire as an IMDG
> before knowing it as a strongly consistent, highly distributed.
>
I agree - I tend to write it as "distributed, in-memory database" for the
commercial GemFire version.
--
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/
Re: Apache Geode is....
Posted by Sai Boorlagadda <sb...@pivotal.io>.
As a newbie, I suggest to change the order of the “adjectives of gemfire” to keep "in-memory database" to-gether.
Apache Geode is a highly distributed, strongly consistent, in-memory database built to support low-latency transactional applications.
Don’t know if it makes any difference? all I know is gemfire as an IMDG before knowing it as a strongly consistent, highly distributed.
Sai
> On Sep 18, 2015, at 12:28 PM, Gregory Chase <gc...@pivotal.io> wrote:
>
> On Fri, Sep 18, 2015 at 12:24 PM, John Blum <jb...@pivotal.io> wrote:
>
>> Tried to comment, but there is no "comment" section accessible to me on
>> the page. I am getting an error when visiting the page (even after logging
>> in).
>>
>> [image: Inline image 1]
>>
>> For someone reason, it seems I am an unknown user. I did have to
>> re-register an account with Apache Confluence as it would seem my original
>> account got lost.
>>
>>
> I won't claim to be a power user of the wiki, but I don't see any
> restrictions that would disallow comments by a registered user.
>
>
> --
> 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/
Re: Apache Geode is....
Posted by Gregory Chase <gc...@pivotal.io>.
On Fri, Sep 18, 2015 at 12:24 PM, John Blum <jb...@pivotal.io> wrote:
> Tried to comment, but there is no "comment" section accessible to me on
> the page. I am getting an error when visiting the page (even after logging
> in).
>
> [image: Inline image 1]
>
> For someone reason, it seems I am an unknown user. I did have to
> re-register an account with Apache Confluence as it would seem my original
> account got lost.
>
>
I won't claim to be a power user of the wiki, but I don't see any
restrictions that would disallow comments by a registered user.
--
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/
Re: Apache Geode is....
Posted by John Blum <jb...@pivotal.io>.
Tried to comment, but there is no "comment" section accessible to me on the
page. I am getting an error when visiting the page (even after logging in).
[image: Inline image 1]
For someone reason, it seems I am an unknown user. I did have to
re-register an account with Apache Confluence as it would seem my original
account got lost.
On Fri, Sep 18, 2015 at 12:09 PM, Gregory Chase <gc...@pivotal.io> wrote:
> On Fri, Sep 18, 2015 at 12:04 PM, John Blum <jb...@pivotal.io> wrote:
>
> > +1 for in-memory database.
> >
> >
> Hi John and team,
> I've taken all the feedback so far and written a complete redraft of the
> website text based on a presumed new template. This is now posted on the
> wiki.
>
> Please make changes and feedback directly to the wiki:
>
> https://cwiki.apache.org/confluence/display/GEODE/Sept+2015+Website+Refresh+proposal
>
> I will be calling or a vote to accept by next Friday.
>
> --
> 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/
>
--
-John
503-504-8657
john.blum10101 (skype)
Re: Apache Geode is....
Posted by Gregory Chase <gc...@pivotal.io>.
On Fri, Sep 18, 2015 at 12:04 PM, John Blum <jb...@pivotal.io> wrote:
> +1 for in-memory database.
>
>
Hi John and team,
I've taken all the feedback so far and written a complete redraft of the
website text based on a presumed new template. This is now posted on the
wiki.
Please make changes and feedback directly to the wiki:
https://cwiki.apache.org/confluence/display/GEODE/Sept+2015+Website+Refresh+proposal
I will be calling or a vote to accept by next Friday.
--
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/
Re: Apache Geode is....
Posted by John Blum <jb...@pivotal.io>.
+1 for in-memory database.
I think the definition largely depends on the scope of the term; if we talk
about ACID then, sure GemFire/Geode is nearly there with only slight
differences in the semantics of consistency, and even less so within the
context of transactions, so I vote for "*in-memory* database". The real
value in my mind is the HA and shared-nothing architecture which is
absolutely paramount to resiliency in a highly volatile (if not hostile)
environment.
-j
On Fri, Sep 18, 2015 at 7:09 AM, Anthony Baker <ab...@pivotal.io> wrote:
> Some products in this space will use a qualifier (NoSQL, Document, Hadoop)
> in their tagline to put the “database” in context.
>
> Anthony
>
> > On Sep 18, 2015, at 6:07 AM, Michael Stolz <ms...@pivotal.io> wrote:
> >
> > I think we historically went down the "in - memory database" route before
> > the term IMDG became popular.
> >
> > IMDG semantics fit Gemfire better than database semantics do.
> >
> > --
> > Mike Stolz
> > GemFire Principal Product Manager
> > Mobile: 631-835-4771
> > On Sep 17, 2015 9:37 PM, "Greg Chase" <gr...@gregchase.com> wrote:
> >
> >> On Thu, Sep 17, 2015 at 8:42 PM, Anthony Baker <ab...@pivotal.io>
> wrote:
> >>
> >>> What is more than a data grid but less than a database?
> >>>
> >>
> >> Positioning from both are valid. A lot of technologies position off
> >> "database": "Object database", "document database", "in-memory
> database",
> >> "NoSQL Database"
> >>
> >> The question is whether IMDGs are taking on more and more "database
> like"
> >> capabilities and thus can earn that position. Or are there things that
> >> fundamentally IDMGs are unsuitable for, and this same use case would be
> >> unsuitable for Geode.
> >>
> >> I originally wrote IMDG for the short description of Geode since its a
> >> great explanation to explain the highly distributed share-nothing
> >> architecture. At Pivotal we market the technology as an "in-memory
> >> database".
> >>
> >>
> >>> I just had a conversation on the sidelines of a soccer game tonight
> >>> explaining that no we don’t have database semantics but we do more
> than a
> >>> basic IMDG. They had done an exploration previously and had picked up
> >>> hazelcast.
> >>>
> >>
> >> What exactly is meant by "database semantics"? When I usually hear
> people
> >> say that, they really mean RDBMS - tables, and SQL.
> >>
> >> I know certain analysts who believe IMDGs are fundamentally NOT
> databases
> >> because they don't do SQL.
> >>
> >> -Greg
> >>
>
>
--
-John
503-504-8657
john.blum10101 (skype)
Re: Apache Geode is....
Posted by Anthony Baker <ab...@pivotal.io>.
Some products in this space will use a qualifier (NoSQL, Document, Hadoop) in their tagline to put the “database” in context.
Anthony
> On Sep 18, 2015, at 6:07 AM, Michael Stolz <ms...@pivotal.io> wrote:
>
> I think we historically went down the "in - memory database" route before
> the term IMDG became popular.
>
> IMDG semantics fit Gemfire better than database semantics do.
>
> --
> Mike Stolz
> GemFire Principal Product Manager
> Mobile: 631-835-4771
> On Sep 17, 2015 9:37 PM, "Greg Chase" <gr...@gregchase.com> wrote:
>
>> On Thu, Sep 17, 2015 at 8:42 PM, Anthony Baker <ab...@pivotal.io> wrote:
>>
>>> What is more than a data grid but less than a database?
>>>
>>
>> Positioning from both are valid. A lot of technologies position off
>> "database": "Object database", "document database", "in-memory database",
>> "NoSQL Database"
>>
>> The question is whether IMDGs are taking on more and more "database like"
>> capabilities and thus can earn that position. Or are there things that
>> fundamentally IDMGs are unsuitable for, and this same use case would be
>> unsuitable for Geode.
>>
>> I originally wrote IMDG for the short description of Geode since its a
>> great explanation to explain the highly distributed share-nothing
>> architecture. At Pivotal we market the technology as an "in-memory
>> database".
>>
>>
>>> I just had a conversation on the sidelines of a soccer game tonight
>>> explaining that no we don’t have database semantics but we do more than a
>>> basic IMDG. They had done an exploration previously and had picked up
>>> hazelcast.
>>>
>>
>> What exactly is meant by "database semantics"? When I usually hear people
>> say that, they really mean RDBMS - tables, and SQL.
>>
>> I know certain analysts who believe IMDGs are fundamentally NOT databases
>> because they don't do SQL.
>>
>> -Greg
>>
Re: Apache Geode is....
Posted by Michael Stolz <ms...@pivotal.io>.
I think we historically went down the "in - memory database" route before
the term IMDG became popular.
IMDG semantics fit Gemfire better than database semantics do.
--
Mike Stolz
GemFire Principal Product Manager
Mobile: 631-835-4771
On Sep 17, 2015 9:37 PM, "Greg Chase" <gr...@gregchase.com> wrote:
> On Thu, Sep 17, 2015 at 8:42 PM, Anthony Baker <ab...@pivotal.io> wrote:
>
> > What is more than a data grid but less than a database?
> >
>
> Positioning from both are valid. A lot of technologies position off
> "database": "Object database", "document database", "in-memory database",
> "NoSQL Database"
>
> The question is whether IMDGs are taking on more and more "database like"
> capabilities and thus can earn that position. Or are there things that
> fundamentally IDMGs are unsuitable for, and this same use case would be
> unsuitable for Geode.
>
> I originally wrote IMDG for the short description of Geode since its a
> great explanation to explain the highly distributed share-nothing
> architecture. At Pivotal we market the technology as an "in-memory
> database".
>
>
> > I just had a conversation on the sidelines of a soccer game tonight
> > explaining that no we don’t have database semantics but we do more than a
> > basic IMDG. They had done an exploration previously and had picked up
> > hazelcast.
> >
>
> What exactly is meant by "database semantics"? When I usually hear people
> say that, they really mean RDBMS - tables, and SQL.
>
> I know certain analysts who believe IMDGs are fundamentally NOT databases
> because they don't do SQL.
>
> -Greg
>
Re: Apache Geode is....
Posted by Greg Chase <gr...@gregchase.com>.
On Thu, Sep 17, 2015 at 8:42 PM, Anthony Baker <ab...@pivotal.io> wrote:
> What is more than a data grid but less than a database?
>
Positioning from both are valid. A lot of technologies position off
"database": "Object database", "document database", "in-memory database",
"NoSQL Database"
The question is whether IMDGs are taking on more and more "database like"
capabilities and thus can earn that position. Or are there things that
fundamentally IDMGs are unsuitable for, and this same use case would be
unsuitable for Geode.
I originally wrote IMDG for the short description of Geode since its a
great explanation to explain the highly distributed share-nothing
architecture. At Pivotal we market the technology as an "in-memory
database".
> I just had a conversation on the sidelines of a soccer game tonight
> explaining that no we don’t have database semantics but we do more than a
> basic IMDG. They had done an exploration previously and had picked up
> hazelcast.
>
What exactly is meant by "database semantics"? When I usually hear people
say that, they really mean RDBMS - tables, and SQL.
I know certain analysts who believe IMDGs are fundamentally NOT databases
because they don't do SQL.
-Greg
Re: Apache Geode is....
Posted by Anthony Baker <ab...@pivotal.io>.
What is more than a data grid but less than a database?
I just had a conversation on the sidelines of a soccer game tonight explaining that no we don’t have database semantics but we do more than a basic IMDG. They had done an exploration previously and had picked up hazelcast.
Anthony
> On Sep 17, 2015, at 4:16 PM, Greg Chase <gr...@gregchase.com> wrote:
>
> On Wed, Sep 16, 2015 at 2:27 PM, Justin Erenkrantz <ju...@erenkrantz.com>
> wrote:
>
>>
>> Here's my $.02 of how I might describe it:
>>
>> Apache Geode is an in-memory strongly consistent highly distributed
>> database built to support low-latency transactional applications.
>>
>> That comes in at 16 words.
>>
>> Cheers. -- justin
>>
>
> I like it. Added some commas, but otherwise +1
>
> Apache Geode is an in-memory, strongly consistent, highly distributed
> database built to support low-latency transactional applications.
Re: Apache Geode is....
Posted by Greg Chase <gr...@gregchase.com>.
On Wed, Sep 16, 2015 at 2:27 PM, Justin Erenkrantz <ju...@erenkrantz.com>
wrote:
>
> Here's my $.02 of how I might describe it:
>
> Apache Geode is an in-memory strongly consistent highly distributed
> database built to support low-latency transactional applications.
>
> That comes in at 16 words.
>
> Cheers. -- justin
>
I like it. Added some commas, but otherwise +1
Apache Geode is an in-memory, strongly consistent, highly distributed
database built to support low-latency transactional applications.
Re: Apache Geode is....
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On Mon, Sep 14, 2015 at 7:44 PM, Greg Chase <gr...@gregchase.com> wrote:
> First panel is a short description explaining what Geode is:
>
> "Apache Geode is a distributed, in-memory data grid and integrated
> messaging queue built to support low latency transactional applications at
> extreme scale."
Here's my $.02 of how I might describe it:
Apache Geode is an in-memory strongly consistent highly distributed
database built to support low-latency transactional applications.
That comes in at 16 words.
Cheers. -- justin