Need advice about which tool to choose?Ask the StackShare community!
Kyoto Tycoon vs Scylla: What are the differences?
What is Kyoto Tycoon? A handy cache/storage server. Kyoto Tycoon is a lightweight database server with auto expiration mechanism, which is useful to handle cache data and persistent data of various applications. Kyoto Tycoon is also a package of network interface to the DBM called Kyoto Cabinet.
What is Scylla? Next Generation Cassandra. Real-time big data database, with scale-up performance of 1,000,000 IOPS per node, scale-out to 100s of nodes and 99 latency of less than 1 msec.
Kyoto Tycoon and Scylla can be categorized as "Databases" tools.
Scylla is an open source tool with 5.18K GitHub stars and 615 GitHub forks. Here's a link to Scylla's open source repository on GitHub.
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.
CassandraCassandra 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.
ScyllaDBScylla 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
Cassandrai love syclla for pet projects however it's license which is based on server model is an issue. thus i recommend cassandra
ScyllaDBBy 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.
The Gentlent Tech Team made lots of updates within the past year. The biggest one being our database:
We decided to migrate our #PostgreSQL -based database systems to a custom implementation of #Cassandra . This allows us to integrate our product data perfectly in a system that just makes sense. High availability and scalability are supported out of the box.
Pros of Kyoto Tycoon
- RESTful API2
- Simple, persistent Key-Value Store2
- Easy setup1
Pros of ScyllaDB
- Replication2
- Fewer nodes1
- Distributed1
- Scale up1
- High availability1
- Written in C++1
- High performance1
