Apache Geode: Distributed, in-memory database
geode.incubator.apache.org
Apache Geode: Distributed, in-memory database
1–10 of 65 posts
Re: Apache Geode: Distributed, in-memory database
#2Let me guess: it's written in Java?
Re: Apache Geode: Distributed, in-memory database
#3Let me guess: it's written in Java?
Yes.
Why are all Apache projects are written in Java?
Re: Apache Geode: Distributed, in-memory database
#4Re: Apache Geode: Distributed, in-memory database
#5Let me guess: it's written in Java?
Yes. Why are all Apache projects are written in Java?
Apache isn't written in Java :)
Re: Apache Geode: Distributed, in-memory database
#6Re: Apache Geode: Distributed, in-memory database
#7Let me guess: it's written in Java?
Yes. Why are all Apache projects are written in Java?
All: this is a major project (with a long history: http://geode.incubator.apache.org/about) and a major release. It deserves a substantive thread, so please let's not get sidetracked by a language troll.
Re: Apache Geode: Distributed, in-memory database
#8Re: Apache Geode: Distributed, in-memory database
#9Feedback on the documentation:
It's not immediately obvious to me how Geode is different from Redis. When would I want to use Geode over Redis, and vice versa?
Re: Apache Geode: Distributed, in-memory database
#10Feedback on the documentation: It's not immediately obvious to me how Geode is different from Redis. When would I want to use Geode over Redis, and vice versa?
Redis and in-memory data grids are pretty different animals. I would characterize IMDG's like Geode to be concurrent write intensive, and have flexible data models. It also scales out better than Redis in a more automated fashion.
Redis is a great read-intensive cache. It also has a powerful data model, but you have to use their data models. Example: If you want to run calculations on lists or sets, they have powerful operations you can call.
IMDG's such as Geode were built with the rise of automated trading in the finance industry.