Re:Apache Geode: Distributed, in-memory database
by finnh on Thursday November 19, 2015 @03:57PM
(#10597599)
> - 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.
Re:Apache Geode: Distributed, in-memory database
by fweespeech on Thursday November 19, 2015 @05:13PM
(#10598091)
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
by eloff on Thursday November 19, 2015 @06:33PM
(#10598468)
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
by GregChase on Thursday November 19, 2015 @08:33PM
(#10599014)
Geode is write-intensive, and generally optimizes for consistency over availability. That being said - there's a lot built into Geode to ensure availability as well.
Re:Apache Geode: Distributed, in-memory database
by fweespeech on Friday November 20, 2015 @12:19AM
(#10599746)
Fair enough but read-only in the event of a network partition is a viable real world use case.
Re:Apache Geode: Distributed, in-memory database
by markito on Thursday November 19, 2015 @05:10PM
(#10598079)
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
by metatype on Thursday November 19, 2015 @03:56PM
(#10597597)
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
by tuyguntn on Thursday November 19, 2015 @04:02PM
(#10597636)
from docs at[1] they only support SELECT statements in OQL, calling object method in query reminds me Esper complex event processing engine.
[1] - http://geode-docs.cfapps.io/docs/getting_started/querying_qu...
- 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.