IBM watsonx.data vs. Amazon Redshift

Datastax Cassandra is a Java based linearly scalable NoSQL database, best-in-class tunable performance, fault tolerant, distributed, masterless, time series database and has easy-to-use administration and monitoring functionality with opscenter. Configured correctly there is no downtime and no data loss. The documentation is exhaustive, and the community is agile and supportive, and Datastax provides good support. For all these reasons, Datastax Cassandra has become a NoSQL technology of choice for many platforms. However it has some time investment on infrastructure and regular operational tasks, and if you do not have bandwidth for it, a managed NoSQL solution like DynamoDB might be more appropriate. Also if you have search needs on Cassandra and do not have corresponding Spark/Solr setup, Datastax Cassandra might not be ideal for you.

Incentivized

If the number of connections is expected to be low, but the amounts of data are large or projected to grow it is a good solutions especially if there is previous exposure to PostgreSQL. Speaking of Postgres, Redshift is based on several versions old releases of PostgreSQL so the developers would not be able to take advantage of some of the newer SQL language features. The queries need some fine-tuning still, indexing is not provided, but playing with sorting keys becomes necessary. Lastly, there is no notion of the Primary Key in Redshift so the business must be prepared to explain why duplication occurred (must be vigilant for)

Incentivized

• It doesn't just store data but unlocks potential. I am able to analyse a vast amount of information, identify trends, and predict future outcomes.
• It not only gives me high quality but accessible data as well. It handles missing values, outliers and feature engineering with case.

Incentivized

• Redshift is fully managed. Small teams do not have the resources to maintain a cluster. CloudWatch metrics are provided out-of-the-box, and it is easy to configure alarms.
• Redshift's console allows you to easily inspect and manage queries, and manage the performance of the cluster.
• Redshift is ubiquitous; many products (e.g., ETL services) integrate with it out-of-the-box.
• Writing .csvs to S3 and querying them through Redshift Spectrum is convenient.

Incentivized

• Integration complexity with Security Tools while watsonx.Data is well-suited for native tools, but integration with third-party security tools requires custom connectors or manual ETL pipelines. which leads to an increase in setup time.
• User interface and query time can be improved.

Incentivized

• It could benefit from adding data integrity and programming tools common to other database management systems.
• Amazon Redshift is based on PostgreSQL 8.0.2. That version of PostgreSQL was released in December 2006. While PostgreSQL was much improved since then, the new features were not implemented in Redshift. Many basic features are missing from it.
• Primary keys can be declared but not enforced. Referential integrity (foreign keys) can be declared but not enforced. UNIQUE and CHECK constraints are not supported and cannot be declared.
• IDENTITY can be declared on a column, and Redshift will put unique values into it. However: IDENTITY values in the newly inserted rows won’t be incremental or sequential. To implement a sequential number, you need to write your own custom code.
• There are no stored procedures in Redshift. We are writing SQL script files, and then parsing and running them one statement at a time from a Python program. This also enabled us to implement execution-time error logging.
• In SQL scripts, to check for the row count of affected rows, a complicated join query against some system tables or views has to be executed.
• Data Control Language (DCL) does not exist. No statements like IF, WHILE, DO, RAISERROR, etc.
• On performance of views… Views do not “pass-through” a query parameter which is a potential problem for performance.
• When selecting against a view with the WHERE clause outside of the view, the inner query of the view will be executed first without consideration for the WHERE clause, and only then the WHERE clause will be applied.
• Certain clauses of SQL work many times faster than other clauses. So be careful and test your statements for performance earlier rather than later, especially if working with a large data set.
• There was a situation when DELETE FROM JOIN was unacceptably slow. Replacing JOIN with the USING clause made DELETE instantaneous.

Incentivized

As an open source technology Cassandra can be readily used with or without any commercial support. DataStax provides value-added services and features, and in the end it is up to individual situations to strike a balance between the desirability of such support/service versus the associated cost.

Incentivized

DataStax has a good community built around it and has amazing scalability options. Though the initial setup is a bit costly, in the long run, it makes up for it. It also has powerful monitoring tools and a clean UI.

Incentivized

Overall it serves all our aspects of data management like data cleaning, data manipulation, and data reporting on the cloud platform. We can create stored procedures and triggers in it very easily as all the options are self suggested in it. We can easily attach the results of ARS to the other tools as well for drawing the statistical results.

Incentivized

good recovery features

Incentivized

scalable product

Incentivized

We have had a few situations where we caused an outage or something has gone wrong and we are able to get a support person to offer live help within minutes. The escalation process is excellent - the best I've seen - and the support team is incredibly strong. Outside of emergencies, the team is very helpful with general questions and working through data model exercises and the subscription I believe still comes with some hours to help get the data model reviewed.

The support was great and helped us in a timely fashion. We did use a lot of online forums as well, but the official documentation was an ongoing one, and it did take more time for us to look through it. We would have probably chosen a competitor product had it not been for the great support

Incentivized

easy to follow documentation, support is there when needed

Incentivized

use saas service

Incentivized

I believe DataStax Enterprise is the best in class. There are some things that are different with the schema-less systems but I found DataStax Enterprise easiest to implement while evaluating. The replication is on par or better than others in practice. We are evaluating Astra in our test environment and that has additional benefits we are looking forward to using.

We evaluated [Amazon] Redshift vs BigQuery vs Amazon EMR, back in 2014. Back then BigQuery cost was slightly higher than that of [Amazon] Redshift price structure. Amazon EMR, needs lots more management (Admin tasks) and EMR is designed to be ephemeral and not designed to be a data store. [Amazon] Redshift was ideal with the price structure, performance and ROI[.]

Incentivized

cognos integration works great

Incentivized

• for one automation project, we managed to cut cloud storage costs by a third through IBM watsonx.data's lakehouse optimization
• data integration projects have had a 20 % reduction in turnaround times. Can only imagine how that will improve with the Claude partnership

Incentivized

• It allows for an almost seamless integration of our data which can then be used by other departments for analytical purposes.
• No in house resources are needed for keeping the data alive and performing backup/migration tasks of the data in its end state.

Incentivized