We performed a comparison between Informatica PowerCenter, Oracle Data Integrator (ODI), and Spring Cloud Data Flow based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."PowerCenter performs well during data transformation and optimization."
"Can manage a huge quantity of data and provide reliability."
"It reduces a lot of legacy coding."
"We use Informatica PowerCenter to transfer the transitional database to and from the data warehouse. This is very efficient as it enables us to quickly find our data reports and the data, so we can build AI models."
"The partitioning and optimization to help enhance our development is a very valuable aspect of Informatica PowerCenter."
"The most valuable feature of Informatica PowerCenter is data transformation and user-friendliness."
"UI-based ability to create data mapping."
"It's a complete package, which is why we use this solution."
"The most valuable features of ODI are the knowledge modules, such as the Loading Knowledge module and the Check Knowledge module, they are helpful. We can check for the constraints in ODI. That helps in figuring out what are the constraints that are the primary keys created in the tables. We can check them with the Check Knowledge module."
"It allows us to use many languages to develop and to integrate practically all the technologies of the Oracle suite as well as those from non-Oracle vendors."
"ODI's most valuable features are it utilizes the database engine and is very lightweight."
"ODI's best features are customization, integration with other versioning tools, and the ability to define new knowledge modules."
"It's scalable."
"I like that Oracle Data Integrator (ODI) has a straightforward setup and offers good technical support."
"The most valuable feature of ODI is the to use of the whole ETL to create a data lake."
"Besides loading data, we do most of our transformations in ODI."
"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 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."
"The most valuable feature is real-time streaming."
"If you want to transfer a ZIP file, it is a pain. You need to use Command-Line. Sometimes we just want to transfer a file. It should be easy to move them from A to B."
"The performance of Informatica PowerCenter could improve."
"Informatica PowerCenter could improve the data threshold for large sets of data. Additionally, they should add real-time integration."
"The initial setup is not straightforward. You need expertise to do it."
"There can be scalability issues. Huge amounts of data ingestion will impact performance."
"Unstructured data handling is an important area with a shortcoming that needs improvement in the solution."
"The UI is outdated and old-fashioned, at least in our current version. Also, we have experienced some stability issues with the Workflow Monitor application."
"PowerCenter could be improved by having more big data components. Normally, we prefer Informatica as a relational database, but nowadays, companies are trying to understand and use big data components. I think it would be useful if we had more chances to create a hub ecosystem because customers try to use some data integration tasks by SQL, Spark and Spark codes, and Scala, but at the end of the day, the company will understand that we need to trace all the steps. An ETL tool is a must for that company, if we're talking about the regulated industries like finance, telcos, etc. If Informatica's biggest ecosystems feature were okay, I would prefer to use it."
"The solution lacks some functions and features."
"If you have something like Cisco on top of it, you will have endless problems."
"The initial setup is a bit complex compared to other tools."
"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."
"Reverse engineering is complicated and challenging to manage."
"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 stability of the software could be improved. Sometimes, the software just crashes. "
"Overall the product is fine, but sometimes its reports unknown errors while we compile ETL scripts."
"Some of the features, like the monitoring tools, are not very mature and are still evolving."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"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."