Data Analyst at a wholesaler/distributor with 51-200 employees
Real User
Top 5
2024-04-24T19:40:08Z
Apr 24, 2024
If the proof of concept goes through, we might use it for data analytics and KPIs. We could also use it to store our EDI for our customers instead of using a value-added network for EDI transactions. We could handle all that in-house. You could use Cassandra to scale by setting up a tiny copy on the internal network. My vision for it is that instead of paying a third party for EDI transactions, we could handle everything in-house. This way, both we and our customers benefit. If it turns out to be cheaper, that's great. If it's more expensive, I can inform my boss, and we can decide whether to continue. I rate the tool's ease of integration with existing infrastructure a six out of ten. I rate the overall product an eight out of ten.
I rate the product a six out of ten. I recommend conducting a simple proof of concept to test and validate Cassandra for specific use cases. Start with a small chunk of your actual use case, and then proceed accordingly. It's crucial not to overlook the logic part during implementation, as this can have a significant impact on the overall success of the deployment.
I am using the latest version of the solution. PostgreSQL has limitations while adding columns. Cassandra is a self-managed service. If someone wants a solution with a heavy write speed of time series data and knows the queries they need to make before creating the table, they should invest in the product. Overall, I rate the solution an eight out of ten.
Senior System Integration Engineer at Hitachi Data Systems
Real User
Top 10
2022-12-20T14:45:22Z
Dec 20, 2022
I rate the solution a six out of ten because I haven't found any consistency in its performance, which is not aligned with what we see on the back end. The solution is good, but its documentation can be improved.
Senior Cloud Architect at a transportation company with 10,001+ employees
Real User
2022-09-23T16:49:44Z
Sep 23, 2022
Because it's such a unique database system, I would counsel people to use it only in situations where it solves a specific problem. You can't just replace it like you can with SQL Server and Postgres, which are kind of corollaries. Cassandra's a bit of a unique animal. It solves specific problems, and you should choose it when you need to solve problems that it fits. I would rate this solution as an eight out of ten.
Senior Database Engineer at S&P Global Market Intelligence
Real User
2022-05-18T19:39:10Z
May 18, 2022
I would recommend this solution to others. Cassandra is a highly scalable NoSQL database system where if you have a lot of data, for example, in the millions in volumes of data you can. I rate Cassandra an eight out of ten.
It's important to have a data architect or consultant on hand who knows the technology and can judge whether it's a suitable product for the use case. I rate this solution eight out of 10.
Senior Director IP led Services (PES) at a computer software company with 1,001-5,000 employees
Real User
2021-05-18T17:36:10Z
May 18, 2021
When it comes to the ease of use of a solution it is not what matters, I do not look at it from this perspective. I am mostly concerned with the performance because as a developer and expert, we do not look at that easy of use we just want it to perform well. Even if it is a little bit complex, it is okay. The performance is the only thing I care about because if you are tech-savvy you should be good enough to write a code and use the function. I would recommend this solution to others. I rate Cassandra an eight out of ten.
I would suggest not over-complicating things. If you really need to have heavy write and you are okay with building keys by yourself, then go with Cassandra. If not, then the culture base is there, MongoDB is there. And MongoDB is the best one. If you are not enterprise, then don't kill yourself. Once I started working on Cassandra, the biggest lesson for me was needing to build. I need keys to retrieve data. If my key and the primary key is not well settled or well configured, then it is very tough for me to read data. I would rate this solution a seven out of 10.
My first Cassandra project was with a project introduced to us by Facebook. That was ten years ago. There was a time I tried using it a couple of months ago, and I completed the project for Upwork for Cassandra. Right now, I have another project which is using a Cassandra cluster which is under my management. Previously, I had quite a big Cassandra cluster of about 100 nodes and about 500 terabytes of data. Overall, I would rate the solution nine out of ten.
It's a good tool and it's a growing tool. The support is good. I would definitely recommend it. I would rate Cassandra a nine out of ten. Nothing is perfect but I believe that continuous improvements are coming.
Managing Director at a tech services company with 1-10 employees
Real User
2020-05-25T07:16:44Z
May 25, 2020
We don't use this solution like a common database. It's really for people using big data, BI and other analytic software. You need to have the right use case to take this product. I would rate this solution a nine out of 10.
Cassandra is a distributed and scalable database management system used for real-time data processing.
It is highly valued for its ability to handle large amounts of data, scalability, high availability, fault tolerance, and flexible data model.
It is commonly used in finance, e-commerce, and social media industries.
If the proof of concept goes through, we might use it for data analytics and KPIs. We could also use it to store our EDI for our customers instead of using a value-added network for EDI transactions. We could handle all that in-house. You could use Cassandra to scale by setting up a tiny copy on the internal network. My vision for it is that instead of paying a third party for EDI transactions, we could handle everything in-house. This way, both we and our customers benefit. If it turns out to be cheaper, that's great. If it's more expensive, I can inform my boss, and we can decide whether to continue. I rate the tool's ease of integration with existing infrastructure a six out of ten. I rate the overall product an eight out of ten.
I rate the product a six out of ten. I recommend conducting a simple proof of concept to test and validate Cassandra for specific use cases. Start with a small chunk of your actual use case, and then proceed accordingly. It's crucial not to overlook the logic part during implementation, as this can have a significant impact on the overall success of the deployment.
I am using the latest version of the solution. PostgreSQL has limitations while adding columns. Cassandra is a self-managed service. If someone wants a solution with a heavy write speed of time series data and knows the queries they need to make before creating the table, they should invest in the product. Overall, I rate the solution an eight out of ten.
We use fix people for the maintenance of the solution. The team consists of engineers and developers. I rate Cassandra an eight out of ten.
I rate the solution a six out of ten because I haven't found any consistency in its performance, which is not aligned with what we see on the back end. The solution is good, but its documentation can be improved.
Because it's such a unique database system, I would counsel people to use it only in situations where it solves a specific problem. You can't just replace it like you can with SQL Server and Postgres, which are kind of corollaries. Cassandra's a bit of a unique animal. It solves specific problems, and you should choose it when you need to solve problems that it fits. I would rate this solution as an eight out of ten.
I would recommend this solution to others. Cassandra is a highly scalable NoSQL database system where if you have a lot of data, for example, in the millions in volumes of data you can. I rate Cassandra an eight out of ten.
It's important to have a data architect or consultant on hand who knows the technology and can judge whether it's a suitable product for the use case. I rate this solution eight out of 10.
I rate Cassandra a nine out of ten.
When it comes to the ease of use of a solution it is not what matters, I do not look at it from this perspective. I am mostly concerned with the performance because as a developer and expert, we do not look at that easy of use we just want it to perform well. Even if it is a little bit complex, it is okay. The performance is the only thing I care about because if you are tech-savvy you should be good enough to write a code and use the function. I would recommend this solution to others. I rate Cassandra an eight out of ten.
I would suggest not over-complicating things. If you really need to have heavy write and you are okay with building keys by yourself, then go with Cassandra. If not, then the culture base is there, MongoDB is there. And MongoDB is the best one. If you are not enterprise, then don't kill yourself. Once I started working on Cassandra, the biggest lesson for me was needing to build. I need keys to retrieve data. If my key and the primary key is not well settled or well configured, then it is very tough for me to read data. I would rate this solution a seven out of 10.
My first Cassandra project was with a project introduced to us by Facebook. That was ten years ago. There was a time I tried using it a couple of months ago, and I completed the project for Upwork for Cassandra. Right now, I have another project which is using a Cassandra cluster which is under my management. Previously, I had quite a big Cassandra cluster of about 100 nodes and about 500 terabytes of data. Overall, I would rate the solution nine out of ten.
It's a good tool and it's a growing tool. The support is good. I would definitely recommend it. I would rate Cassandra a nine out of ten. Nothing is perfect but I believe that continuous improvements are coming.
We don't use this solution like a common database. It's really for people using big data, BI and other analytic software. You need to have the right use case to take this product. I would rate this solution a nine out of 10.