Good nosql DB
What do you like best about the product?
Scalability, perforamnce and easy to adopt.
What do you dislike about the product?
AI support need to be improved. i would like to learn more about vector DB features.
What problems is the product solving and how is that benefiting you?
High scalability problem solved.
High Performance
What do you like best about the product?
ScyllaDB is designed for high throughput and low latency, handling millions of operations per second with low latencies. It is built in C++ rather than Java (which Cassandra uses), which allows it to avoid the overhead of the JVM and make better use of system resources.
ScyllaDB supports multi-threading and shared-nothing architecture, making it able to take advantage of modern multi-core CPUs and scale horizontally with ease.
What do you dislike about the product?
Steep learning curve for new users
Smaller ecosystem and community
Operational complexity for on-premise deployments
Memory usage concerns
Lack of rich query features compared to some document databases
What problems is the product solving and how is that benefiting you?
ScyllaDB is solving several key problems commonly faced by organizations that deal with large volumes of data and require high-performance, scalable solutions.
Cheap and blazing fast
What do you like best about the product?
Documentation and support from Scylla team
What do you dislike about the product?
Couldn’t find one as far now. Other than easy integration
What problems is the product solving and how is that benefiting you?
Low latency applications where replacing dynamodb
Best replacement for Cassandra/Bigtable
What do you like best about the product?
Shard per core architecture.
Low cost compared to cassandra and others.
Uses same CQL as used in cassandra so it is drop in replacement
Simple to setup and integrate with help of scyllaDB team.
Is able to handle very high write ops efficiently.
What do you dislike about the product?
Sometimes there can be prod issues due to human error if they forget to migrate their scylla endpoints to new ip as informed by scylladb cloud team
What problems is the product solving and how is that benefiting you?
Maintaining different types of counters for all users like views, clicks, etc.
Scylla DB is a more consistent and scalable product.
What do you like best about the product?
Easily scalable based on the requirements and it is more consistent when compared to other products.
What do you dislike about the product?
As of now everything is fine with ScyllaDB
What problems is the product solving and how is that benefiting you?
Scylla DB resolves the latency issues especially on high loads.
Fast and scalable
What do you like best about the product?
Easy programming of the database and connections
What do you dislike about the product?
Tough to learn at first because not much experienced people on sites like stackoverflow
What problems is the product solving and how is that benefiting you?
NoSQL
ScyllaDB
What do you like best about the product?
low latency and high throughput, Cassandra-compatible, automatically shards
What do you dislike about the product?
complex learning curve, Lightweight Transaction Limitations
What problems is the product solving and how is that benefiting you?
handling real-time workloads
Impression of ScyllaDB
What do you like best about the product?
low cost and maintenance, high performance and low latency
What do you dislike about the product?
not very good explaination for the design architecture that is eay to understand.
What problems is the product solving and how is that benefiting you?
Cassandra has limitations and DynamoDB is not portable.
very promising database
What do you like best about the product?
robust and fast and allow multi concurrency for huge data
What do you dislike about the product?
new and need some knowledge base, aside from that all is good
What problems is the product solving and how is that benefiting you?
fast and huge covarage
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.
