IBM Cloud Pak for Integration vs WhereScape RED comparison

"Cloud Pak for Integration is definitely scalable. That is the most important criteria."

"It is a stable solution."

"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."

"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."

"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."

"The tool supports multiple target update methods."

"WhereScape RED has improved our business's ability to generate needed reporting without requiring a large team of developers to manually code all of the necessary plumbing."

"The most valuable feature is the metadata generated code."

"It has a built-in automatic scheduling environment."

"WhereScape is really helpful in terms of architecture data. Everything is one of automation. Two people can do thousands of tables in one day or two. It saves a lot of time."

"Naturally produces a way to easily debug your DW data solutions."

"I found the initial setup very easy."

"Data transformations and rollups are easy to accomplish."

"The initial setup is not easy."

"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."

"Its queuing and messaging features need improvement."

"Enterprise bots are needed to balance products like Kafka and Confluent."

"The pricing can be improved."

"They need a more robust support center. It has been a bit difficult to find solutions to problems that are out-of-the-box."

"The ability to execute SSIS projects within WhereScape would be nice because we have a lot of packages that are too cumbersome to recreate."

"The solution can be a little more user-friendly on enterprise-level where people use it."

"No support for change data capture or delta detection - that must be custom coded ."

"Jobs cannot be deleted via the deployment package. When deploying from dev to QA or production, a job has to be retired. The job has to be manually removed from the target environment."

"Customization could be better."

"The scheduled jobs which are run by the WhereScape scheduler seem to be a strangely separate animal. Unlike all other WhereScape objects, jobs cannot be added to WhereScape projects. Also, unlike all other objects, jobs also cannot be deleted using a WhereScape deployment application."

"It could use a tool to diagnose what is missing from the environment for WhereScape to install successfully."

"The solution's pricing model is very flexible."

"It is an expensive solution."

"Speed to market of a warehouse solution at a relatively inexpensive price point."

"Factor in the price of specialized consulting who know this product. They're hard to find and expensive."

"Our company purchased a corporate unlimited license."

"ROI is at least 10 times."