We performed a comparison between Oracle Data Integrator (ODI), StreamSets, 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."Oracle provides great documentation."
"Integration with all systems is easy with Oracle Data Integrator, and it is easy to use. I have not used any other product, but with Oracle Data Integrator, we can easily connect to an ERP system, an SAP system, or a cloud application."
"The CAEM is very useful in its modularity and portability."
"It's scalable."
"The product has an ELT approach."
"The installation of the client ODI Studio is easy."
"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 best features are customization, integration with other versioning tools, and the ability to define new knowledge modules."
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"The scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy."
"One of the things I like is the data pipelines. They have a very good design. Implementing pipelines is very straightforward. It doesn't require any technical skill."
"It's very easy to integrate. It integrates with Snowflake, AWS, Google Cloud, and Azure. It's very helpful for DevOps, DataOps, and data engineering because it provides a comprehensive solution, and it's not complicated."
"The most valuable would be the GUI platform that I saw. I first saw it at a special session that StreamSets provided towards the end of the summer. I saw the way you set it up and how you have different processes going on with your data. The design experience seemed to be pretty straightforward to me in terms of how you drag and drop these nodes and connect them with arrows."
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"I really appreciate the numerous ready connectors available on both the source and target sides, the support for various media file formats, and the ease of configuring and managing pipelines centrally."
"The tool supports multiple target update methods."
"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."
"Quickly develops a data warehouse for our organization with documentation and can track back/forward features."
"I like the data vault implementations."
"It has a built-in automatic scheduling environment."
"RED generates comprehensive documentation and regenerates it as quickly as things changes, but it also provides impact documentation."
"Support is absolutely excellent, efficient, and timely."
"An area for improvement in Oracle Data Integrator (ODI) is real-time integration. Currently, my company has a workaround to implement real-time integration, an area on which Oracle must focus more. Real-time integration should be easier in Oracle Data Integrator (ODI). Another area for improvement in Oracle Data Integrator (ODI) is integration with more publishers and subscribers rather than just database integrations."
"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."
"It would be really good if Oracle considered enabling the tool to integrate with some other platforms that are deprecated simply for commercial reasons"
"If there was an add-on tool to hide the performance issues and solve them for me, then I might be interested in that as it would provide me value."
"I would only point out some minor bugs or glitches in the development interface (ODI studio)."
"We used a third party to do the implementation of ODI."
"It has been very good. Just recently, I've faced an issue, but I solved it somehow. While integrating with a file, I faced an issue where I wanted output files, and I had used the text field limited quotations, but at the end of the file, there was a line breakage for the last column. So, we just removed the text field because it was not working correctly for us."
"The tool should improve its pricing. It prevents the application of Oracle ODI on small and medium projects in countries like Croatia, Germany, or the US. While there are no technological obstacles to using it, the high price makes it unfeasible for projects with smaller budgets."
"In terms of the product, I don't think there is any room for improvement because it is very good. One small area of improvement that is very much needed is on the knowledge base side. Sometimes, it is not very clear how to set up a certain process or a certain node for a person who's using the platform for the first time."
"I would like to see further improvement in the UI. In addition, upgrades are not automatic and they should be automated. Currently, we have to manually upgrade versions."
"Sometimes, when we have large amounts of data that is very efficiently stored in Hadoop or Kafka, it is not very efficient to run it through StreamSets, due to the lack of efficiency or the resources that StreamSets is using."
"There aren't enough hands-on labs, and debugging is also an issue because it takes a lot of time. Logs are not that clear when you are debugging, and you can only select a single source for a pipeline."
"Visualization and monitoring need to be improved and refined."
"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."
"Sometimes, it is not clear at first how to set up nodes. A site with an explanation of how each node works would be very helpful."
"One thing that I would like to add is the ability to manually enter data. The way the solution currently works is we don't have the option to manually change the data at any point in time. Being able to do that will allow us to do everything that we want to do with our data. Sometimes, we need to manually manipulate the data to make it more accurate in case our prior bifurcation filters are not good. If we have the option to manually enter the data or make the exact iterations on the data set, that would be a good thing."
"No support for change data capture or delta detection - that must be custom coded ."
"The solution can be a little more user-friendly on enterprise-level where people use it."
"Project-based searching of data objects in the data warehouse browser needs to be improved."
"The ability to execute SSIS projects within WhereScape would be nice because we have a lot of packages that are too cumbersome to recreate."
"They need a more robust support center. It has been a bit difficult to find solutions to problems that are out-of-the-box."
"It could use a tool to diagnose what is missing from the environment for WhereScape to install successfully."
"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."
"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."
Earn 20 points
