Exceptional Performance Boost with ScyllaDB!
What do you like best about the product?
The best aspect of ScyllaDB lies in its unparalleled performance. It handles massive datasets seamlessly, ensuring swift and reliable data access. The scalability is a game-changer for growing projects, providing a robust foundation for evolving requirements
What do you dislike about the product?
While ScyllaDB excels in performance, the learning curve can be steep for newcomers. Improved documentation or beginner-friendly resources could enhance the onboarding experience. This was the problem I've personally faced while moving mongodb to scylladb. I've just recently came across to these scylladb live masterclasses, so I think they are working on this problem.
What problems is the product solving and how is that benefiting you?
ScyllaDB has been a game-changer by addressing critical issues in project building. Its robust performance and scalability effectively handle the challenges of working with large datasets, ensuring my project operates seamlessly even as it grows. As a fresher, navigating complex database structures used to be a stumbling block, but ScyllaDB's user-friendly approach has significantly eased the learning curve. Additionally, its efficient data access and retrieval mechanisms have streamlined development, saving time and resources. In essence, ScyllaDB's solutions have transformed potential roadblocks into opportunities for smoother project development.
Good tutorials to learn the database
What do you like best about the product?
the database is a nosql db. you do not need to learn comploicated sql. only need to use it like normal function call. the db itself is fast and stable
What do you dislike about the product?
the data returns can be inconsistent sometime
you need to be careful regarding your use case
What problems is the product solving and how is that benefiting you?
fast efficient, and it provides a layer to me to protect my relational database from being overloaded
Very nice NoSQL database
What do you like best about the product?
It's a very nice database, clean and usefull.
What do you dislike about the product?
Actually, just few people uses. I want that database be huge.
What problems is the product solving and how is that benefiting you?
When i knew that ifood and discord will use him, i know there will be a nice database.
great product
What do you like best about the product?
features, functions, alternatives to other databases,
What do you dislike about the product?
new in market, unsure if it fits into my environment
What problems is the product solving and how is that benefiting you?
cloud features, hopefully save time and money
Using ScyllaDB
What do you like best about the product?
1. modern DB
2. scalability inbuild
3. suitable for distributed systems
4. No-SQL type is suitable for dynamic schema
5. very fast compared to other DB
6. opensource so it could be used in business
What do you dislike about the product?
1. significantly less documentation
2. no good source for video tutorials to get an understanding of the DB
3. not many written articles available as a tutorial
4. very less information on StackOverflow or other Q&A websites
What problems is the product solving and how is that benefiting you?
I tried some DB options for distributed systems, which are NoSQL type. so DB systems are DynamoDB ,Cassandra , Mongo and ScyllaDB . ScyllaDB is really good and also open source. but due to very few tutorials and videos available, its tough to understand how to proceed. Still I tried , and it was a good experience
Great NoSQL Database
What do you like best about the product?
It is compatible with Amazon Dynamo Database API
What do you dislike about the product?
While using LWT, it uses too much IO and provides quite a low throughput
What problems is the product solving and how is that benefiting you?
ScyllaDB serves as a no-SQL database for my distributed systems. I use its Alternator feature that is compatible with my Amazon DynamoDB API.
Scylla DB quickly became my favourite NoSQL DB
What do you like best about the product?
The DynamoDB compatible API! Being a serverless advocate I've used DynamoDB heavily in the past. When the requirement came along for an on premise option, ScyllaDB allowed for seamless integration with existing code and architectures.
What do you dislike about the product?
Outside of the usual painpoints and adoptions for new DB's, I can't say there is anything specific I dislike about ScyllaDB that can't also be said about other DB technologies!
What problems is the product solving and how is that benefiting you?
A fast and efficient NoSQL DB that allows for on premise Single table design DB's (Key overloading) allowing for a single backend codebase written originally for DynamoDB
A solution that offers good performance and flexibility to its users
What is our primary use case?
Our company currently uses Scylla for our products since we are in the process of migration from Postgres.
Our company is reimplementing the user data pipeline and needs faster results. We found Scylla to be preferable for our use case from the alternatives we evaluated.
What is most valuable?
User-defined type in Scylla allows for data to be consistent. The performance aspects of Scylla are good, as always. The product's flexibility allows us to use Cassandra SDK with it while also being able to migrate from DynamoDB to it. A good point about Scylla is that it can be used extensively.
What needs improvement?
It has just been a month or so for me with Scylla. The documentation of Scylla is an area with shortcomings and needs to be improved. Improvement of documentation is needed considering that I work with Java. We currently use a data stack model, which is actually for Cassandra. There is no different dependency for Scylla, so it's adding a wrapper on the SDK that Cassandra supports, and we end up just using it.
I think it's good as it is. I don't have any input on what needs to be added in Scylla.
For how long have I used the solution?
I have experience with Scylla for around two months. Currently, I am learning more about Scylla. I am using the solution's latest version. My company is a system integrator. We have different verticals, and one of it is that we are moving into is integrating, which is running our product as a binary in our enterprise solution and on clients' machines.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
Currently, we are involved with Scylla's prototype version. For the project that I am working on, Scylla is not being used, and it is not just the case with my project alone but also with a huge number of projects because they are moving to cloud-agnostic architecture. We are moving all the DynamoDB databases to Scylla. Within a year or so, all of our DynamoDB databases will be replaced.
To be able to rate Scylla's scalability, we would need time since we are using its prototype.
Which solution did I use previously and why did I switch?
Previously, I have used MongoDB for other projects.
We actually are not switching from MongoDB. We have a couple of alternatives for what we are building, and we wanted to know about SQL because we may have to change our schema quite a bit because we used to have a lot of metadata, and that's why the traditional RDBMS will have to split the columns instead of rows, making it very intense.
How was the initial setup?
Scylla is a cloud-based solution. We are moving to a cloud-agnostic architecture, so we would have different instances based on our enterprise solution or the client.
Whether to use a private or public cloud depends on the requirements of our clients.
In my local environment, the installation part was quite easy because it's a Docker installation. I don't know about the remote installations with Kubernetes because that is managed by the cloud tech team.
What other advice do I have?
I have been working on the solution for around a month, so it is mostly the people involved in the cloud tech department who look at things like the maintenance of the solution, an area in which I have no idea.
A weird error can pop up owing to the flaws in the documentation, because of which I am using an ORM tool to interact with the database. If required in a particular use case, I return a list of objects, or a list of a user data type, when it throws an error indicating that I should reimplement the codec. When I changed the codec to set, it started working fine. The aforementioned issue was not figurable even in Stack Overflow.
Overall, I rate the solution an eight out of ten.
Verbose and compact setup.
What do you like best about the product?
Complexicity, to understand you have basic knowledge about database models,containers and abillity to not give up.
What do you dislike about the product?
Feels kinda overwhelming,the harder you go, the bigger might challenge be for you.
What problems is the product solving and how is that benefiting you?
storage issues,also firewal setup necessary. containers management
scylla DB the wonderful DB
What do you like best about the product?
Fast access and very good for data intensive workloads and latency is minimum.
What do you dislike about the product?
More focused on cloud and less support for on prem database users
What problems is the product solving and how is that benefiting you?
scylladb is providing alternatives and covering the shortcomings of other databases such as cassandra and dynamo db etc and helping in reduction of costs.
