ScyllaDB Enterprise

What do you like best about the product?

ScyllaDB performance is very fast and steady.

ScyllaDB events are useful and easy to follow.

Learning from the community sessions is simple.

The overall ecosystem feels strong and growing.

What do you dislike about the product?

Nothing major to dislike.

It would help if ScyllaDB had simple built-in user access features.

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

The community support is great. We can depend on ScyllaDB for stable and always-on performance. It helps us increasing our revenue.

What do you like best about the product?

ScyllaDB is fast, highly scalable, and efficiently uses all CPU cores. It handles millions of operations per second with consistent performance, scales easily by adding nodes, and has excellent, practical documentation.

What do you dislike about the product?

It’s self-managed and requires a fairly deep level of technical knowledge to operate effectively.

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

ScyllaDB solves the performance bottlenecks common in other NoSQL databases.
While many systems struggle with high latency and slow reads under heavy load, ScyllaDB delivers extremely fast and consistent read performance, even at large scale.
It fully utilizes all CPU cores and scales horizontally without losing speed, eliminating slowdowns and bottlenecks during peak traffic.
In practice, this means near real-time responses and a much more efficient infrastructure.

What do you like best about the product?

I like ScyllaDB for its cluster-node solution and the ease with which I can define data replicas. This feature is particularly beneficial in use cases where MongoDB and Cassandra might fall short. When I attempted similar tasks with another database, the process was far more complicated and confusing. As a developer who is primarily focused on application code, I appreciate not having to devote excessive time to database hurdles. Additionally, the initial setup of ScyllaDB seemed easy for me, which is advantageous for someone new to the product. These aspects make my experience with ScyllaDB more efficient and enjoyable, encouraging me to explore the platform further in the training documentation.

What do you dislike about the product?

Nothing at this moment, I need to use more before.

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

ScyllaDB simplifies cluster-node solutions and defining data replicas, ideal for developers like me who focus on application code rather than database complexities.

What do you like best about the product?

I use ScyllaDB as a NoSQL database for appending message data before transitioning it to downstream services, where its efficiency stands out significantly. ScyllaDB is cheaper than DynamoDB, yet it offers comparable or sometimes even superior performance, which is highly beneficial for cost-effective scalability. I appreciate the SQL-like syntax that ScyllaDB provides, which enhances the usability by making it easier to query and manage data. The shard-per-core architecture is particularly impressive because it allows us to maximize CPU utilization, squeezing out extraordinary levels of performance, which is critical for our intensive processing needs. Additionally, the support team at ScyllaDB has been incredibly active and helpful in troubleshooting, making the transition smooth and instilling confidence in the adoption of their system.

What do you dislike about the product?

I find the lack of support for lightweight transactions (LWT) across nodes or partitions challenging. This limitation makes it difficult to handle transactions in a manner similar to PostgreSQL, where transactions can touch multiple tables in the database. Additionally, I would appreciate built-in support for retries, which is currently lacking and impacts the ease of handling transactions effectively.

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

I use ScyllaDB as a cost-effective NoSQL database with performance comparable to DynamoDB. It optimizes CPU usage with shard per core, supports SQL-like syntax, and aids in appending message data efficiently.

What do you like best about the product?

The performance is really impressive - we're seeing much lower latency and way better throughput compared to what we had before. The fact that it's compatible with Cassandra made our migration pretty smooth, and honestly, the speed improvements alone made it worth the switch.

What do you dislike about the product?

It took us a good bit of time to get comfortable with it, especially coming from a simpler database setup. The docs are okay but sometimes feel a bit sparse - we spent way too much time googling things during our initial deployment. Would love to see more practical examples and troubleshooting tips for when things don't go as planned.

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

We needed a database that could handle our growing data volumes without slowing down. ScyllaDB solved our performance bottlenecks - queries that used to take seconds now finish in milliseconds. It's also helping us save on infrastructure costs since we need fewer nodes to handle the same workload. The scalability has been a game changer for us as our user base keeps growing.