A solution that offers good performance and flexibility to its users
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What other advice do I have?
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.
SCyllaDB review
What do you like best about the product?
It is:
-> Open Source
-> NoSQL Database
-> Greatly compatible with Apache Cassandra
What do you dislike about the product?
The installation process could be a bit easier,and the usage could be a more simpler for the new users and little non techie guy
What problems is the product solving and how is that benefiting you?
NoSql helps me creating db without any worries
ScyllaDB Review from a Student
What do you like best about the product?
I really enjoy ScyllaDB's ease of use when it comes to setting up serverless clusters. The documentation and resources are top-notch. The reliability and the options to fine-tune consistency with the various replication factors and consistency levels are fantastic for anyone who needs to ensure high consistency and or availability. Overall from my first experience with ScyllaDB, I'd recommend it to anyone who wants to explore big data and NoSQL databases.
What do you dislike about the product?
In my eyes, I think Scylla is excellent, but I think its use case is out of reach for the standard developer or student. Due to the focus on large-scale data operations, it sacrifices things like relational queries. It's a niche use case that not every project or company will fit, so I think that should be kept in mind.
What problems is the product solving and how is that benefiting you?
It's helping me solve large scale data storage for logging
Software Engineer
What do you like best about the product?
More performant and scalable as its build using c++(lightweight).
Integrated caching
What do you dislike about the product?
lack of support for transactions.
customer service support and availability should be improved.
What problems is the product solving and how is that benefiting you?
scalablity & performance
Scylladb Review
What do you like best about the product?
It's compatibility with Apache Cassandra
Flexible data model that enables easier data access
Cost effective for organizations that look returns on their initial investments
What do you dislike about the product?
More on the maintenance efforts to maintain Scylladb
Difficulty in debugging & analyzing issues, given its complexity
Limited supported on secondary indexes.
What problems is the product solving and how is that benefiting you?
DB as a Service, is an absolute best way to resolve issues wrt database provisioning.
Better at-fault tolerance and resilience
Overall better performance, availability, fault-tolerance & resilience.
ScyllaDB provides lightweight database and the great support.
What do you like best about the product?
We've been using ScyllaDB since 2018. It is lightweight and easy to maintain. Compared to the other DBs we are using today, ScyllaDB is more cost-efficient. I would also like to give a thumbs up to the support team.
What do you dislike about the product?
To be honest, I don't have too much on my mind.
What problems is the product solving and how is that benefiting you?
We need a lightweight and cost-efficient database to store our data. ScyllaDB does give us such benefits, and we believe it will provide us with more. We recently leveraged Scylla Alternator to replace the usage of DynamoDB.
Performant db even in low resources
What do you like best about the product?
I like how Scylladb performs best, even under very low resources with very little TCO.
What do you dislike about the product?
It is relatively new, so has not much support for all languages like, PHP. Learning curve is also higher for the first time.
What problems is the product solving and how is that benefiting you?
We are using it specifically for our needs to serve high throughput writes.
ScyllaDB: the new age nosql and better replacement of Cassandra.
What do you like best about the product?
Lightweight and fast as it's built on C++
Way better than Cassandra (that we previously used). Low latency and high throughput as compared to Cassandra.
What do you dislike about the product?
Data export can be improvised.
The cost is a bit high, especially the yearly one.
What problems is the product solving and how is that benefiting you?
We are using Scylla for our alerting service, where we persist our subscription-related data and other domain related data.
Previously we are storing these in Cassandra, and during the scaling, we are facing issues when the load is very high at times.
With Scylla, we were able to take care of latency problems and scale out the service during peak hours.
A robust real-time Nosql DB supporting lightweight transactions
What do you like best about the product?
We chose ScyllaDB over Redis because of the Lightweight transactions it supports. Being able to update partitions was a necessity for us. Also, university.scylladb.com has good resources for getting started for a new user.
What do you dislike about the product?
There are no tools for bulk importing and exporting of the data. We have to build and maintain our custom applications.
What problems is the product solving and how is that benefiting you?
We use ScyllaDB for caching the session state of user sessions on our gaming apps. With each time interval or stage the users advance to, we have to read the state, take decisions and then update the state within a few milliseconds. We also use this key-value store for finding out highly active users, users who are dormant and users who are stuck at any stage for long time. With our confidence growing in ScyllaDB, we are planning to build many other use cases around the database.
Performance Champion with simplicity
What do you like best about the product?
The performance of ScyllaDB is one of its key advantages. It is the perfect option for applications that demand real-time data processing because it is built to handle massive amounts of data with extremely low latencies. ScyllaDB can manage expanding data demands without suffering from performance deterioration because it is very scalable.
The fault-tolerance of ScyllaDB is another important aspect. Data is replicated across numerous nodes since it is meant to operate in a distributed context. This minimises any potential downtime by ensuring that even if one node fails, the data may still be accessed from other nodes.
ScyllaDB is also simple to use and incorporate into existing applications. It supports a range of programming languages and has a number of integrations with other
What do you dislike about the product?
ScyllaDB can be more sophisticated than some other NoSQL databases, despite the fact that it is intended to be simple to use and integrate into current applications. The technical knowledge needed to deploy and configure it could be a hurdle for some enterprises.ScyllaDB is designed to handle only a few types of data, including time-series data and key-value data. Although it can manage different forms of data, it might not be the greatest option for applications that call for more intricate data models.ScyllaDB is a newer database, so it's possible that it has a less developed ecosystem than some other databases. This implies that compared to more established databases, ScyllaDB may have fewer resources, tools, and third-party connectors available.
What problems is the product solving and how is that benefiting you?
The major problem which scylladb is solving is performance, which includes low latency and high throughput. Our systems relies on performant databases and scylladb definitely helps out in this case.
