Reliable data management with great reliability and performance
What is our primary use case?
We dump a lot of our data, such as every entry created with respect to when a user rides a scooter, every record gets updated to ScyllaDB. It is used as a single source of truth and it manages massive data.
We support various business use cases, including mobility, where data about driver allocations get updated. We currently have twenty clusters and more than one hundred nodes.
How has it helped my organization?
The performance and scalability are good, and we hardly see any major issues with ScyllaDB. Updates are reliable and help the organization handle large datasets effectively.
What is most valuable?
To be honest, not really. We were sold on the pitch, offering better compaction and ROI, but we did not experience these benefits.
What needs improvement?
From a sales pitch standpoint, it needs to deliver on promises of better ROI and compaction. Additionally, ticketing and support systems could be improved due to the time it takes to get answers. There's also an issue with compatibility when attempting to switch back from the enterprise to the community version.
For how long have I used the solution?
I would say probably five years by now.
What do I think about the stability of the solution?
The performance and stability are fine. We hardly see any major issues, and from a reliability standpoint, it's all good.
What do I think about the scalability of the solution?
Due to organic growth, we end up upgrading the cluster and adding more nodes. In terms of reliability, it's all good, but specific benefits from scalability were not highlighted.
How are customer service and support?
The technical support and customer service are around a five or six out of ten. Improvements can be made in ticketing and response times.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We used to work with Cassandra. During our initial phases, we found ScyllaDB promising due to its implementation language and maintenance, which led us to adopt it over Cassandra.
How was the initial setup?
Migrating to the enterprise version from the community version is straightforward and supported, but moving back to the community version is complex due to compatibility issues.
What was our ROI?
To be frank, not really. The open-source version sufficed our use case without requiring the costly enterprise version.
What's my experience with pricing, setup cost, and licensing?
The enterprise version comes with a cost of about $300,000 per year, however, we did not experience the promised compaction benefits.
Which other solutions did I evaluate?
We evaluated Cassandra during initial proof of concepts.
What other advice do I have?
I would suggest using ScyllaDB wisely and adhering to best practices, such as regular cleanup since many engineers tend to expand clusters instead of cleaning up data. I would rate ScyllaDB as eight out of ten.
ScyllaDB - Very useful for use-cases which requires low latency and high performance and scalability
What do you like best about the product?
We are using ScyllaDB Cloud on GCP. Its very usefull in large volume datasets handling. ScyllaDB cloud delivers superior performance, lower latencies, and resilience.
It is very usefull in high read write operations, where very low latency is expected.
Migration to ScyllaDB from existing NoSQL DB was very easy.
Spring Boot based integration was easy to implement.
What do you dislike about the product?
Subscription fee is bit on higher side, it can be made simpler. Pay as you go model will help customers.
What problems is the product solving and how is that benefiting you?
We are using to build a dataset for post trade operations and data quality management.
ScyllaDB - Next Gen Solution, ready to disrupt the market
What do you like best about the product?
1. High Performance
2. Compatibility with Cassandra
3. Low Latency and Scalability
4. Efficient Use of Hardware
5. Automatic Sharding and Load Balancing
6. Self-Tuning and Self-Optimizing
7. High Availability and Fault Tolerance
8. Rich Ecosystem and Tools
9. Cheap
What do you dislike about the product?
1. Complexity in Setup and Configuration
2. Resource-Intensive
3. Limited Ecosystem Compared to More Established Databases
4. Compatibility with Cassandra Is Not Perfect
What problems is the product solving and how is that benefiting you?
using as an alternative of aws
Understanding ScyllaDB's Sharding and Data Distribution Mechanisms
What do you like best about the product?
I admire ScyllaDB's low latency performance, efficient use of resources through C++ architecture, smooth scalability. Also, Cassandra's API compatibility enables high throughput for real-time data processing application for large dataset.
What do you dislike about the product?
ScyllaDB is characterized by limited support for complex queries and secondary indexes, which hinder's performance in certain use cases that require more sophisticated querying capabilities beyond basic workloads.
What problems is the product solving and how is that benefiting you?
I appreciate ScyllaDB's solutions to high-performance, scalable NoSQL challenges. It addresses limitations in traditional databases, enabling efficient handling of large datasets & real-time analytics.
Excellent DB for analytics application
What do you like best about the product?
ScyllaDb helped me in creating an analytics application for credit card company. We used scyllaDB for its scalibility and faster access of records. Due to its scalability feature we were able to scale our instance to billions of records.
What do you dislike about the product?
I believe some improvements can be done as third party integration are limited in scyllaDB
What problems is the product solving and how is that benefiting you?
We had used PostgreSQL earlier to store last few credit transactions for business puposes, but as user base grew, we started facing slower response time. We migrated our database to scyllaDB and increased the product efficiency by 43% as scyllaDB is faster and scalable. We also performed some analytics for business user to take some business decisions using the scyllaDB features.
Fast Adapting and High Performance DB
What do you like best about the product?
It is fast adapting and poplur db in industry. Its performance is very good as well as a well fault Tolerance capability
Also it supports built-in data replication for high availability and no single point of failure
What do you dislike about the product?
It is Relatively new in the market : Newer compared to some established databases, which might mean fewer third-party integrations.
What problems is the product solving and how is that benefiting you?
We use it as a KV database and also as our json based config store which stores the capacity and inventory of the product.
ScyllaDB "The ideal solution in the NoSQL space"
What do you like best about the product?
It is easy to implement and use for OLTP and OLAP
What do you dislike about the product?
It is not easy to copy large volumes of data for archiving based on a date ranges within a short period of time
What problems is the product solving and how is that benefiting you?
ScyllaDB has become a cost-effective alternative to SQL databases like Oracle or SQL server and it also runs efficiently with minimal overhead reducing the Total Cost of Ownership (TCO), which is important for me in managing large cluster of systems.
High-Performance NoSQL Database
What do you like best about the product?
I highly recommend giving ScyllaDB a try. ScyllaDB is a powerful, open-source database that serves as a drop-in replacement for Apache Cassandra and is designed to make the most of modern hardware.
What I like best about ScyllaDB is its blazing fast performance and efficient use of modern hardware. It takes full advantage of multi-core CPUs, RAM, and SSDs, delivering much better performance compared to similar NoSQL databases like Cassandra. The automatic tuning and self-optimization features also stand out, as they reduce the need for constant manual configurations, making it easier to maintain peak performance without much effort. Additionally, ScyllaDB's ability to scale easily while maintaining low latency, even with a massive data load, is another key feature I appreciate.
What do you dislike about the product?
While ScyllaDB is Cassandra-compatible, Cassandra has a more mature and extensive ecosystem with more third-party tools and integrations.
What problems is the product solving and how is that benefiting you?
High Throughput with Low Latency
Scalability without Downtime
ScyllaDB’s auto-tuning and self-optimizing features reduce the operational complexity
Efficiency, Speed, and Reliability
What do you like best about the product?
Scylla DB is designed to be highly efficient, utilizing a close-to-the-metal design that minimizes overhead. This allows it to achieve higher performance with fewer resources compared to other NoSQL databases like Apache Cassandra. For instance, Scylla DB can reduce cluster sizes to a fraction of what Cassandra requires, leading to significant cost savings and greater return on investment
What do you dislike about the product?
Setting up ScyllaDB can be more complex compared to other databases like PostgreSQL or ClickHouse. It may not be as straightforward and could require more effort to get everything running smoothly.
What problems is the product solving and how is that benefiting you?
ScyllaDB solves several key problems, offering high throughput and low latency
Offers encryption and supports APIs, making it great for distributed systems
What is our primary use case?
We use ScyllaDB, a NoSQL database, as a distributed system to store customer data. My last project was in telecommunications, where we stored caller information like phone numbers, names, and scam tags for a scam call protection service. We handled insert, update, and other operations since the back-end AI system needed daily data inputs. We ran scripts to add the data to ScyllaDB across two AWS regions: US East and US West. One Scylla node handled requests, synchronizing data with its peer nodes. During the POC phase, we testedperformance, read/write operations, and latency and chose the right consistency levels for ourneeds. After that, we moved to production.
How has it helped my organization?
We are customers, not partners, and we’ve used ScyllaDB to implement an application in our company.
What is most valuable?
The best features of ScyllaDB are how it synchronizes data and its failover system. There's a unique formula to decide the number of nodes you need and the minimum required, which I find helpful. It also offers encryption and supports APIs, making it great for distributed systems
and scaling databases across different regions. While it's easy to use, having prior experience helps configure it properly. There are many configurations; if you don't understand them, you might mess up the design. So, understanding your system's needs, like whether it requires more read or write operations, is crucial for setting up the correct configuration.
What needs improvement?
We faced several challenges while integrating ScyllaDB into our AWS environment. One common issue was that a security port wasn’t opened on one node, preventingdata synchronization across clusters. We noticed the data wasn’t syncing correctly when we saw different record counts in other regions. After investigating, we found that the port was closed in one AWS region. Once we opened the port, the data synchronization across all nodes resumed as expected.
For how long have I used the solution?
I've been using ScyllaDB for the last three years. Initially, we worked on some POC projects and deployed one live project into production.
What do I think about the stability of the solution?
I've had some stability issues with ScyllaDB. For instance, if one of the nodes in a cluster goes down, sometimes the APIs or command line tools don't work to read the node's status. You might need to restart the node to bring it back up manually. It can be challenging if the node'sstate gets messed up and must be cleaned before re-adding it to the cluster. Based on stability, I'd rate it a seven out of ten. However, since we're using the free version, it might be more stable with the paid version, which could be a nine out of ten.
What's my experience with pricing, setup cost, and licensing?
The paid version of ScyllaDB is not that expensive. The main advantage of the paid version is direct support from the ScyllaDB team, which can resolve issues faster—typically within a day, compared to two to three days with the free version. The paid version also offers better guidance and support, while the free version has good documentation and is more high-level. I’d rate their support team nine out of ten because of the quick responses from their community.
What other advice do I have?
I would recommend ScyllaDB to others. It’s a great product built on Cassandra, with added advantages. For newcomers, it’s a distributed database with excellent scalability and performance and very low latency for all kinds of operations. Overall, I’d rate ScyllaDB an eight out of ten.
