We performed a comparison between Oracle Data Integrator (ODI), Spring Cloud Data Flow, and WhereScape RED based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."What I found most valuable in Oracle Data Integrator (ODI) is that it integrates well with almost all technologies currently being used in my company."
"ODI's most valuable features are it utilizes the database engine and is very lightweight."
"One of the standout features of ODI is its ability to prepare everything on a vertical level and create reusable components, which adds to its value."
"The CAEM is very useful in its modularity and portability."
"It's scalable."
"The most valuable feature of ODI is the to use of the whole ETL to create a data lake."
"It can integrate with more recent databases like Cassandra, Hadoop, and other more recent Big Data databases."
"I like that Oracle Data Integrator (ODI) has a straightforward setup and offers good technical support."
"The most valuable features of Spring Cloud Data Flow are the simple programming model, integration, dependency Injection, and ability to do any injection. Additionally, auto-configuration is another important feature because we don't have to configure the database and or set up the boilerplate in the database in every project. The composability is good, we can create small workloads and compose them in any way we like."
"There are a lot of options in Spring Cloud. It's flexible in terms of how we can use it. It's a full infrastructure."
"The most valuable feature is real-time streaming."
"The product is very user-friendly."
"RED has provided us the ability to integrate, stage, and transform data from diverse sources into an enterprise-grade data warehouse which meets the needs of my organization, but it also enables us to easily and quickly make ETL or DW changes."
"It has a built-in automatic scheduling environment."
"Quickly develops a data warehouse for our organization with documentation and can track back/forward features."
"This is a fantastically robust DW tool that will make you at least 10 times faster in producing a DW."
"Support is absolutely excellent, efficient, and timely."
"I like the data vault implementations."
"The tool supports multiple target update methods."
"The most valuable feature is the metadata generated code."
"The performance of the user interface is in need of improvement."
"ODI could improve by being more user-friendly. Informatica, which is also an ETL tool, similar to ODI, but Informatica is very user-friendly, easy to use, and simple to integrate, compared to ODI. ODI has many features, put them all together, and sometimes we get confused about which ones to use, which ones not to use."
"The solution lacks some functions and features."
"There are certain things where it can be improved. Initial solution setup seems a bit complex at the start, it should be improved because it becomes bit tough for a novice to get started on this. Sometimes error description is not helpful to understand the problem it gives some generic type of errors which are at times not that helpful to understand the underlying root cause of the issue."
"The interface of ODI could be improved. For example, navigating and finding functions can be difficult. For example, you have to know which step you need to go to look at where your job status is. The logical step is a bit complex compared to other tools. It's much easier to get a graphical view, but with ODI, it's graphical, plus you have to know all the other pieces that fit around it. You have to think about the logical and physical aspects."
"I rate it a seven out of 10 because there is room for growth because ODI is still new, in comparison to Informatica, which is a mature product."
"At present, when multiple steps are executed in parallel in the load plan and errors occur, the error handling mechanism does not function correctly."
"The initial setup is a bit complex compared to other tools."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"Some of the features, like the monitoring tools, are not very mature and are still evolving."
"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."
"Spring Cloud Data Flow could improve the user interface. We can drag and drop in the application for the configuration and settings, and deploy it right from the UI, without having to run a CI/CD pipeline. However, that does not work with Kubernetes, it only works when we are working with jars as the Spring Cloud Data Flow applications."
"The ability to execute SSIS projects within WhereScape would be nice because we have a lot of packages that are too cumbersome to recreate."
"No support for change data capture or delta detection - that must be custom coded ."
"Project-based searching of data objects in the data warehouse browser needs to be improved."
"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."
"Improve the object renaming ability (it works, but it could be more automated)."
"Technical support isn't the best."
"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."
"The solution can be a little more user-friendly on enterprise-level where people use it."
Earn 20 points
