Best Key Value database
What do you like best about the product?
I think this is the best key value database so for. Also the query results are faster compare to other databases and the sql used here are same like other available database. It's replication and high availability feature is very good
What do you dislike about the product?
Nothing so for. I liked it so for. Exploring more features of the same.
What problems is the product solving and how is that benefiting you?
Faster query results
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.
Sycallldb - A Promising Debugging Tool with Room for Growth
What do you like best about the product?
Sycallldb has proven to be an outstanding debugging tool that offers a potent combination of user-friendliness, versatility, performance, and a robust feature set. It has earned its place as a compelling choice for developers looking to streamline their debugging process and efficiently resolve complex software issues. As development continues, I look forward to witnessing further advancements that will solidify Sycallldb's position as a top-tier debugging solution.
What do you dislike about the product?
Lack of Specific Examples: The review mentions that Sycallldb has a robust set of features, but it could benefit from providing specific examples of those features in action. This would help readers understand how the tool functions and what benefits they can expect.
Limited Critique: While the review mentions that there is room for improvement, it doesn't delve deeply into specific areas that need enhancement. Providing more concrete suggestions for improvement would add value to the review.
Comparison to Other Tools: The review doesn't compare Sycallldb with other debugging tools available in the market. A comparison could help readers understand how it stacks up against its competitors and what unique advantages it offers.
What problems is the product solving and how is that benefiting you?
Performance Scalability, Low latency, Scalability & high availability
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.
I have been using Scylla DB for 3 years in a big company of food delivery in Brazil
What do you like best about the product?
Scylla DB is fast at writing and reading.
What do you dislike about the product?
You can't have models that change often.
What problems is the product solving and how is that benefiting you?
The system that I developing receives more than 1 million Kafka messages per day and it's necessary to save all messages as a dominium of the system. The writing needs to be fast and Scylla DB solves it.
Peace of mind
What do you like best about the product?
One of the best tools to come have come across in the last 10 years. The ease of set up, and configuration is next to none. Good on you ScyllaDB, keep rolling out the new features and updates.
What do you dislike about the product?
it's indeed some learning curve; not necessarily a dislike or a negative; may be it's my learning potential. it's a work in progress and I'm sure it'll only ease as I use it more.
What problems is the product solving and how is that benefiting you?
The ease of use and solving my business case, which in this case was working a Key value Database, is a major advantage. The user community is quite strong too so it helps voicing out concerns.
Efficient, Scalable and Easy to Maintain
What do you like best about the product?
Ease of use and scale as per the usage. We have been using ScyllaDB in Production from last 5 years. I started with version 2.x and now running 5.x. Very smooth operations.
What do you dislike about the product?
Not much. However, the backup and restored process could be improved more.
What problems is the product solving and how is that benefiting you?
We store our systems (IoT Smart Solar Systems) data in ScyllaDB. We use that data for improving our systems' performance, improve our operations and Product in future versions.
