Need advice about which tool to choose?Ask the StackShare community!
The problem I have is - we need to process & change(update/insert) 55M Data every 2 min and this updated data to be available for Rest API for Filtering / Selection. Response time for Rest API should be less than 1 sec.
The most important factors for me are processing and storing time of 2 min. There need to be 2 views of Data One is for Selection & 2. Changed data.
Scylla can handle 1M/s events with a simple data model quite easily. The api to query is CQL, we have REST api but that's for control/monitoring
Cassandra is quite capable of the task, in a highly available way, given appropriate scaling of the system. Remember that updates are only inserts, and that efficient retrieval is only by key (which can be a complex key). Talking of keys, make sure that the keys are well distributed.
By 55M do you mean 55 million entity changes per 2 minutes? It is relatively high, means almost 460k per second. If I had to choose between Scylla or Cassandra, I would opt for Scylla as it is promising better performance for simple operations. However, maybe it would be worth to consider yet another alternative technology. Take into consideration required consistency, reliability and high availability and you may realize that there are more suitable once. Rest API should not be the main driver, because you can always develop the API yourself, if not supported by given technology.
i love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra
Pros of Cassandra
- Distributed119
- High performance98
- High availability81
- Easy scalability74
- Replication53
- Reliable26
- Multi datacenter deployments26
- Schema optional10
- OLTP9
- Open source8
- Workload separation (via MDC)2
- Fast1
Pros of Hazelcast
- High Availibility11
- Distributed Locking6
- Distributed compute6
- Sharding5
- Load balancing4
- Map-reduce functionality3
- Simple-to-use3
- Written in java. runs on jvm3
- Publish-subscribe3
- Sql query support in cluster wide3
- Optimis locking for map2
- Performance2
- Multiple client language support2
- Rest interface2
- Admin Interface (Management Center)1
- Better Documentation1
- Easy to use1
- Super Fast1
Pros of Memcached
- Fast object cache139
- High-performance129
- Stable91
- Mature65
- Distributed caching system33
- Improved response time and throughput11
- Great for caching HTML3
- Putta2
Sign up to add or upvote prosMake informed product decisions
Cons of Cassandra
- Reliability of replication3
- Size1
- Updates1
Cons of Hazelcast
- License needed for SSL4
Cons of Memcached
- Only caches simple types2
Sign up to add or upvote consMake informed product decisions
What is Cassandra?
What is Hazelcast?
What is Memcached?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Hazelcast?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Hazelcast?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+4
+5
+4
+17
+9+17
+42
+47