Need advice about which tool to choose?Ask the StackShare community!
Cassandra vs UnQLite: What are the differences?
Cassandra: A partitioned row store. Rows are organized into tables with a required primary key. Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL; UnQLite: An Embeddable NoSQL Database Engine. UnQLite is a in-process software library which implements a self-contained, serverless, zero-configuration, transactional NoSQL database engine. UnQLite is a document store database similar to MongoDB, Redis, CouchDB etc. as well a standard Key/Value store similar to BerkeleyDB, LevelDB, etc.
Cassandra and UnQLite can be categorized as "Databases" tools.
Cassandra and UnQLite are both open source tools. Cassandra with 5.27K GitHub stars and 2.35K forks on GitHub appears to be more popular than UnQLite with 997 GitHub stars and 102 GitHub forks.
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
i love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra
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.
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 UnQLite
Sign up to add or upvote prosMake informed product decisions
Cons of Cassandra
- Reliability of replication3
- Size1
- Updates1
Cons of UnQLite
- Different compilation for each platform1
Sign up to add or upvote consMake informed product decisions
What is Cassandra?
What is UnQLite?
Need advice about which tool to choose?Ask the StackShare community!
What companies use UnQLite?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with UnQLite?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+5
+17
+42
+26