ScyllaDB Enterprise

What do you like best about the product?

As a software consultant, I find ScyllaDB to be a high-performance, distributed NoSQL database that excels in scalability and low-latency operations. Its compatibility with Cassandra makes migration and integration straightforward, and many users report that it is easier to administer than Cassandra, with less tuning required . While initial setup can be more complex than some relational databases, ScyllaDB’s architecture allows for efficient use of modern hardware and offers robust features such as built-in caching, encryption, and monitoring tools . Integration with existing systems is generally smooth, and the database is frequently used in production by major enterprises for data-intensive workloads . Customer support is strong, especially for enterprise clients, and the active community and regular updates ensure ongoing improvements. However, documentation and some advanced features could be more comprehensive, and secondary indexes may impact write performance . Overall, ScyllaDB is a powerful choice for organizations needing speed, scalability, and reliable support.

What do you dislike about the product?

While ScyllaDB offers impressive performance and scalability, there are several areas where it falls short for my use cases. The initial setup and configuration can be quite complex compared to more traditional databases like PostgreSQL, often requiring careful resource planning and tuning. Debugging and analyzing issues can also be challenging due to the system’s complexity, and maintenance efforts tend to be higher than expected. I’ve found the documentation lacking in some areas, which makes troubleshooting and advanced configuration more difficult. Additionally, ScyllaDB’s support for transactions is limited, and features like secondary indexes and multi-key transactions are either not fully supported or have notable limitations. The community around ScyllaDB is relatively small, which means finding help or shared experiences outside of official channels can be difficult. These factors combined can make ScyllaDB a less approachable choice for teams without deep NoSQL expertise or those looking for a more mature ecosystem.

What problems is the product solving and how is that benefiting you?

At the moment we are looking for options to be our Database for a new APP that we will launch this year.

What do you like best about the product?

1. Blazing Fast Performance
Latency: Ultra-low latency even at high throughput.

Throughput: Handles millions of operations per second per node.

Example: Users report up to 10x better performance than Cassandra in the same hardware.

What do you dislike about the product?

While it uses CQL, it’s still a NoSQL DB.

Not ideal for relational joins, ad-hoc analytics, or OLAP workloads.

2. Schema Evolution is Painful
Altering schemas, adding indexes or materialized views can impact performance or require careful planning.

3. Learning Curve
New developers may struggle with:

Data modeling that fits Scylla's partition/key-based logic.

What problems is the product solving and how is that benefiting you?

Time-Series Data Storage
Use Case: IoT sensors, monitoring systems, geolocation tracking
Why ScyllaDB:

Efficient partitioning and TTL support

Optimal for append-only, timestamped data

Compact storage with compression

What do you like best about the product?

The best thing about ScyllaDB is it's internal indexing strategy that helps in great performance while retrieving millions of logs data.The inbuilt metrics monitoring software (grafana) is also a really amazing and we does not need to separately setup the monitoring and metrics dashboard. It's well suited for logs, real-time, and time-series data analytics.

What do you dislike about the product?

Sometimes the documentation requires more efforts to understand it's internals. I also felt that learning curve in scylladb is different as compared to other databases like Cassandra. But once, we get enough practice, it's just super easy.

What problems is the product solving and how is that benefiting you?

We have to analyse a lot of logs data, and retrieving and storing those data in scylladb was the best move we did. It just retrieves the data, in miliseconds due to it's performance (especially it's indexing strategy). It's caching mechanism is also helping in making our application faster. And we really upgraded our customer UX by loading more and more data in no time and showing great analytics.

What do you like best about the product?

I like it's performance and very low latency across the globe. It handles massive datasets seamlessly, ensuring swift and reliable data access. It's best for handling time-series data, and when we need real-time analytics.

What do you dislike about the product?

It's a bit different from other NoSQL DBs. And it's documentation is also bit difficult to find ready-made examples for our use case unlike we can find solutions in StackOverflow and Reddit for other databases.

What problems is the product solving and how is that benefiting you?

It's low-latency and amazing performance allowing us to manage a lot of time-series data in real-time without delays. It's caching mechanism is also helping us a lot to make the performance better.

What do you like best about the product?

It’s best for workloads that need High availability across multiple data centers and horizontal scaling. The best thing about ScyllaDB is its low latency nature along with the scaling and high availability. I also like the sessions and workshops organized by ScyllaDB, it helps to get started with the database and integrate it with the existing system.

What do you dislike about the product?

The documentations can be improved as it's hard to follow if you are new to this space Though the sessions, workshops and ScyllaDB university live is best way to get started.

What problems is the product solving and how is that benefiting you?

We were facing issues in scaling our system. When we started using ScyllaDB, things were going much better. The speed is great, and our system is running more smoothly now. It has made our system more stable and reliable, even if there’s a lot of traffic coming into our system.