ScyllaDB for Zee5 Platform
What do you like best about the product?
ScyllaDB has significantly enhanced the Zee5 platform by delivering high performance, low latency, and excellent scalability. Its robust architecture ensures seamless handling of millions of transactions per second, providing our users with a smooth and reliable streaming experience. The ease of management and cost efficiency have reduced our operational burden and infrastructure costs. Moreover, ScyllaDB's outstanding support and active community have been invaluable. Overall, ScyllaDB has proven to be a superior database solution for our needs.
What do you dislike about the product?
Still not much presence in Azure cloud apart from field cloud. Specially when customer expect DBaaS.
What problems is the product solving and how is that benefiting you?
All the problems that we were facing with AWS cloud dynamo db, multiregion support etc. Scylla started with reducing our TCOC with DBaaS feature for AWS and GCP cloud.
ScyllaDB: The NoSQL Beast You Didn’t Know You Needed! + Discord is on SCYLLA!!
What do you like best about the product?
I've recently started learning about ScyllaDB. As an open-source, community-based software, ScyllaDB is a robust and scalable NoSQL database designed to handle modern data needs effectively.
Why ScyllaDB ?
Diverse Flavours:
Open Source: Accessible for startups and small projects.
Enterprise Version: Enhanced features and support for mission-critical applications.
ScyllaDB Cloud: A seamless, scalable DBaaS offering.
No Vendor Lock-In:
No Vendor Lock-in : ScyllaDB can run on-premise or across various cloud hyperscalers, ensuring no vendor lock-in and future-proofing infrastructure decisions.
Performance and Scalability:
High performance and low latency make it an ideal replacement for Apache Cassandra and DynamoDB.
High Scalability: Add nodes vertically without any downtime.
Cost Efficient.
A low-cost solution providing significant savings compared to other NoSQL databases.
Also, we get advanced Features with latest Version 6.0:
The latest version introduces improved data modeling and more!
Community and Support:
A vibrant community and helpful support make it easier to optimize and troubleshoot :)
What do you dislike about the product?
I have limited background of NoSQL Databases. hence, for me, Learning Curve isone thing:
ScyllaDB can have a steep learning curve for those new to NoSQL databases or transitioning from SQL databases.
My other point of view is ScyllaDB can be Resource Intensive:
While it offers high performance, ScyllaDB can be resource-intensive, requiring careful planning and management of infrastructure.
What problems is the product solving and how is that benefiting you?
we are currently using a managed Oracle DB.
Apart from the High end distributed applocations I am trying to understand How ScyllaDB's can be best and effective used for Not so Huge and highly intensive Datasets.
Perfect NoSQL database
What do you like best about the product?
ScyllaDB is a NoSQL database with excellent performance that is ideal for data-intensive applications due to its low latency and high throughput characteristics. Because of its compatibility with Amazon DynamoDB and Apache Cassandra, users of these platforms can make a seamless transfer.
What do you dislike about the product?
Even with its improvements, documentation still needs more best practices manuals.
For people who are not experienced with C++ or Cassandra-based systems, there could be a significant learning curve.
What problems is the product solving and how is that benefiting you?
Low-latency reads and writes
Familiar CQL syntax for those used to Cassandra
High availability and concurrency
Robust support and active community
high power
What do you like best about the product?
it is coordinated and partition tolerance
What do you dislike about the product?
not suited with less data in the apllication
What problems is the product solving and how is that benefiting you?
high data transfer in secs
Scylladb review
What do you like best about the product?
ScyllaDB is highly praised for its impressive performance and scalability. It is designed to handle large volumes of data and high throughput with low latency, making it ideal for real-time applications. The database is compatible with Apache Cassandra, allowing users to switch with minimal effort. Additionally, its shard-per-core architecture ensures efficient resource utilization, leading to better performance on multi-core systems.
What do you dislike about the product?
Despite its advantages, ScyllaDB can be complex to manage and configure, requiring significant expertise to optimize and troubleshoot. Its open-source version lacks some advanced features found in the enterprise version, potentially limiting functionality for some users. Additionally, while it is compatible with Cassandra, there can still be nuances and challenges during migration.
What problems is the product solving and how is that benefiting you?
Operational Complexity
Scalability
Performance Bottlenecks
Self-hosting complexity and the way ScyllaDB counts operations can be confusing and may not reflect actual usage
What is our primary use case?
ScyllaDB is a very seamless product within C++ or something. So, it's faster and all that stuff. Even if it is all good, there is more need for marketing on their website than on the original thing.
Now, if you are a big company, ScyllaDB is a good, robust product. It's a terabyte/petabyte kind of product. But your cost would be one-third or even less with ClickHouse, and it would be smoother and lighter.
What is most valuable?
ScyllaDB is very fast, and I can use it for so many things. But what happened is we pushed a lot of data, and even though it was fast, things started getting weird here and there.
At one point, we could understand why accepting this when you restart something or fix something and it starts working. You feel very smart, like, " Oh yeah, we did it right." But then again, these are the problems we shouldn't be having in the first place.
But it is fast and very distributed. So, let's say you're Google, and you need your server in 500 places, and they all should talk with each other in close proximity. And you deploy ScyllaDB and have a dedicated DevOps version full-time. It's going to work. So, those things are there in ScyllaDB. But, again, it requires a full-time job.
What needs improvement?
It seems we have better options available. So probably don't go for ScyllaDB. The reason is, first, it's very high. It's not as straightforward as, like, Postgres or ClickHouse to set up. It requires a complex setup.
The other problem is what they call. For example, they will say that for up to a million operations, you experience this. But the problem is if they have nine servers, then your one operation is counted as nine operations, not one. So, even though you have one write, they count it as nine. It's like it's just not false premises. You can always host it yourself, but then it's way more complex.
The benefits are not substantially more than those of other databases. It's not that it's slow or anything. It's good enough and all. But it's just that ClickHouse or other databases are simpler and faster and probably provide more features. So, I kind of burn out from the database, and that's why I would keep it small.
For how long have I used the solution?
I tried it for two and a half months.
What do I think about the stability of the solution?
ScyllaDB claims it's very stable under a massive load, and I don't doubt it. We didn't have the database go down due to data load. We had problems with infrastructure showing racks from an infrastructure point of view. I don't blame ScyllaDB for not being stable, but in my experience, it wasn't very smooth when it came to infrastructure. If your infrastructure breaks, you have problems.
Maybe if you use the cloud, you don't have to deal with it, but we didn't use the cloud. We tried to set it up ourselves and faced a lot of problems. Maybe I missed something, but we did it a couple of times, and each time there was a new issue.
What do I think about the scalability of the solution?
At one company, only five people used it for about two to four months. Our team consisted of two or three people who deployed and tested it.
How are customer service and support?
We did talk to the support team for help. And funnily enough, we talked with US support. A lot of marketing people for ScyllaDB sit in Europe. So we talked with people in London, India, and America. They know their stuff. They are good people. They know their product, everything is good.
What they don't know is if you ask any person, "Why should I use ScyllaDB over Clickhouse?" they will probably not give you a good answer. So, that kind of stuff.
The other thing is that people are happy. But then again, if you want support on point, they charge some money. And I think we paid for two, three hours, and then it was extra.
Basically, a lot of companies have a mode for ScyllaDB in the market because ClickHouse is a product of its own, and a lot of companies are already using something called Cassandra. ScyllaDB is bigger and better than Cassandra. It uses less memory and they claim it's five to ten times faster.
How was the initial setup?
It is not easy to setup.
I would rate my experience with the setup a five out of ten, with ten being easy.
What's my experience with pricing, setup cost, and licensing?
It is an expensive tool compared to its competitor.
What other advice do I have?
If you already use Cassandra, you can probably consider using ScyllaDB; otherwise, just avoid it.
Using ScyllaDB isn't that hard. Setting it up on the infrastructure side is the same as Kafka. Using Kafka is a piece of cake, but managing and setting it up is difficult. So, using ScyllaDB is not hard, but there are lots of unknown unknowns that you only discover after you get the bill or have users, and then you need DevOps help.
Overall, I would rate the solution a five out of ten.
Provides access to information directly using SQL language with easy interface
What is our primary use case?
We use the solution to present information for a very big system. The dashboard requires real-time information.
How has it helped my organization?
ScyllaDB provides access to information directly using SQL language.
What is most valuable?
The interface was very easy. The most important things are access to information stored as a time series and the very high speed at which we can query the information.
For how long have I used the solution?
I have been using ScyllaDB for five months.
What do I think about the stability of the solution?
I didn't find any exceptions causing problems. We accessed the data and presented the information very quickly.
What do I think about the scalability of the solution?
The scalability would be great.
How are customer service and support?
The documentation and web page are very easy to read.
How would you rate customer service and support?
How was the initial setup?
The deployment process is moderately complex. One person is enough for it.
We used some of your site's available documentation to deploy ScyllaDB. Following those steps was very straightforward, and we could access the information quickly. The process was very clear and user-friendly.
What's my experience with pricing, setup cost, and licensing?
Due to the speed and availability of the database, customers are willing to pay whatever it takes to access this information. The price is not too high.
What other advice do I have?
It would require about four or five people to handle the maintenance tasks.
The integration with the ecosystem depends on the specific area of use, as numerous applications are complex. Overall, you can access information within this database using comprehensive API and easily integrate it into larger solutions.
I recommend the database to anyone who is using a time storage database.
The database is easy to use, fast, and accessible for applications because the API is straightforward.
Overall, I rate the solution a nine out of ten.
Easy to use
What do you like best about the product?
Scylla allows us to store and retrive data with low latency,
What do you dislike about the product?
We need better documentation for best practices.
What problems is the product solving and how is that benefiting you?
Our engineering team were using Scylla as the central database for our production platform. It allows us to store and retain data with low latency, allowing us to deliver personalized experience.
Review of ScyllaDB for replication and Availability
What do you like best about the product?
It provides replication facility because of which data can be accessed fast from any location. ANd also if there is any data loss, it can be recovred fast. The university courses are also very nice and helped me to grasp the understanding of it in detail.
What do you dislike about the product?
Nothing as such. Expect a standalone windows installer.
What problems is the product solving and how is that benefiting you?
i am not using the product as organization wide, however I am experiencing the same and exploring the scenarios where it could be used in the organization.
A good alternative of cassandra for NoSQL database
What do you like best about the product?
The processing power of ScyllaDB excites me. The no of transactions handled per second is extremely high.
What do you dislike about the product?
Lack of flexibility, scalability. Too many restrictions on DML that makes the job harder.
What problems is the product solving and how is that benefiting you?
It's helping in achieving our SLAs with low latency and high throughput.
