11–20 of 65 posts
Feedback 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?
> Data is persisted in write-optimized disk storage. Consistency checking is configurable between highest performance caching and ACID transactions.
seems pretty different to redis. I don't think Redis does ACID transactions.
hey this is very interesting, it could work as a persistent acid memcached drop-in replacement!
> Gemcached > Geode servers can be configured to talk memcached protocol. hey this is very interesting, it could work as a persistent acid memcached drop-in replacement!
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.
Feedback 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 powerfu…
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…
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... :)
Feedback 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?
With Geode your Redis data structures can scale horizontally.
Feedback 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?
How does Apache Goede compares to Apache Ignite (advertised as "in-memory data fabric"?
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…
200,000 Concurrent ticket Purchases