ScyllaDB Reviews

We use it as a non-relational database. We use it to store two things:

1.  To store audit log data and 
2. blob data, including images with different sizes, like 200kb.

We use it as an image database as well, such as user profile pictures and product catalog promotional pictures.

We got Free Community Software for Managing the Blob data for Cross Data Center & Distributed Cluster

ScyllaDB is a rewrite of Cassandra in C++ and uses a special library called Seastar, which was developed by ScyllaDB. 

Seastar is optimized for I/O operations, which makes it very good compared to Cassandra. Like it's ten times better in terms of performance.

The documentation is good. It integrates easily with our existing data infrastructure.

If you don't have the best computing resources, then it's not easy to set up. In such cases, we have to run ScyllaDB in developer mode.

I have been using it for Seven years. 

I have never faced any problems. As per my use case and our environment, it is stable.

It's pretty good. It offers everything we need at this time. It's a scalable product.

In my organization, all 55 people across six products use ScyllaDB.

We have never contacted customer service and support. It's all working great. So, never needed the support 

Positive

We tried MongoDB & Cassandra. It wasn't scalable at that time, like six or seven years ago. Then we moved to Cassandra and then ScyllaDB.

With best computing resources: If you have good computing resources like CPUs, memory, and especially solid-state drives (SSDs), the installation and configuration are very easy. 

Without the best computing resources: If you don't have the best computing resources, then it's not easy to set up. In such cases, we have to run ScyllaDB in developer mode.

NO

YES

It's free. Only support is costly. So the support is an extra cost, which is expensive.

We tried MongoDB & Cassandra. It wasn't scalable at that time, like six years ago. Then we moved to ScyllaDB.

I would recommend to use it. It is easy for a beginner to learn to use ScyllaDB for the first time. 

Overall, I would rate it a ten out of ten. 

Our company currently uses Scylla for our products since we are in the process of migration from Postgres.

Our company is reimplementing the user data pipeline and needs faster results. We found Scylla to be preferable for our use case from the alternatives we evaluated.

User-defined type in Scylla allows for data to be consistent. The performance aspects of Scylla are good, as always. The product's flexibility allows us to use Cassandra SDK with it while also being able to migrate from DynamoDB to it. A good point about Scylla is that it can be used extensively.

It has just been a month or so for me with Scylla. The documentation of Scylla is an area with shortcomings and needs to be improved. Improvement of documentation is needed considering that I work with Java. We currently use a data stack model, which is actually for Cassandra. There is no different dependency for Scylla, so it's adding a wrapper on the SDK that Cassandra supports, and we end up just using it.

I think it's good as it is. I don't have any input on what needs to be added in Scylla.

I have experience with Scylla for around two months. Currently, I am learning more about Scylla. I am using the solution's latest version. My company is a system integrator. We have different verticals, and one of it is that we are moving into is integrating, which is running our product as a binary in our enterprise solution and on clients' machines.

Stability-wise, I rate the solution a nine out of ten.

Currently, we are involved with Scylla's prototype version. For the project that I am working on, Scylla is not being used, and it is not just the case with my project alone but also with a huge number of projects because they are moving to cloud-agnostic architecture. We are moving all the DynamoDB databases to Scylla. Within a year or so, all of our DynamoDB databases will be replaced.

To be able to rate Scylla's scalability, we would need time since we are using its prototype.

Previously, I have used MongoDB for other projects.

We actually are not switching from MongoDB. We have a couple of alternatives for what we are building, and we wanted to know about SQL because we may have to change our schema quite a bit because we used to have a lot of metadata, and that's why the traditional RDBMS will have to split the columns instead of rows, making it very intense.

Scylla is a cloud-based solution. We are moving to a cloud-agnostic architecture, so we would have different instances based on our enterprise solution or the client.

Whether to use a private or public cloud depends on the requirements of our clients.

In my local environment, the installation part was quite easy because it's a Docker installation. I don't know about the remote installations with Kubernetes because that is managed by the cloud tech team.

I have been working on the solution for around a month, so it is mostly the people involved in the cloud tech department who look at things like the maintenance of the solution, an area in which I have no idea.

A weird error can pop up owing to the flaws in the documentation, because of which I am using an ORM tool to interact with the database. If required in a particular use case, I return a list of objects, or a list of a user data type, when it throws an error indicating that I should reimplement the codec. When I changed the codec to set, it started working fine. The aforementioned issue was not figurable even in Stack Overflow.

Overall, I rate the solution an eight out of ten.

We use the solution for distributed systems. 

ScyllaDB is fast and reliable. It has good performance. 

The product needs to add more features and improve the response time of the support team. 

I have been using the product for more than a year. 

We haven't faced any issues with the solution's stability. 

The solution's deployment is of medium complexity. 

You need to have database experience to use the product. I rate it a seven out of ten. 

Scylla is used as a cache. Once the data is ingested into the product during the initial load, a version of it is stored in Scylla DB, and this is then used by the other transformation services to query and make updates during ongoing loads. That is, it is being queried by other services to make the updates whenever deletes occur.

It is lightweight, and it requires less infrastructure.

Data export, along with how we can purchase the data periodically, needs to be improved so that the storage is within control. Then, we could optimize it even better.

This is not a very old product, and it's seven or eight months old.

We would like to leverage it on the public cloud, but due to some limitations at the moment, it's on the cloud but using IAS. We have virtual machines, and there, we have created the cluster.

It's pretty much stable. We have been in production for six months now, and I haven't seen it go down. We have had a few instances where one or two of the nodes have gone down, but the cluster has been stable.

Scalability in performance is good. We can add more nodes and have more scalability. We have about 200 people using this solution.

Support and the availability of support need improvement. I would give them a six out of ten.

Neutral

The architecture team did some tests and performance benchmarking, and they found out that in comparison to that for other tools almost one eighth or one tenth of the infrastructure was required for Scylla and that the performance was the same.

This is built on using C++, and it's very lightweight, whereas the others were using too much infrastructure. These are some of the reasons why Scylla was chosen.

I believe that there is a yearly licensing cost and that it's expensive.

The architecture team evaluated MongoDB and Cassandra.

Overall, I would give Scylla a seven out of ten for our use case.