"StreamSets’ data drift resilience has reduced the time it takes us to fix data drift breakages. For example, in our previous Hadoop scenario, when we were creating the Sqoop-based processes to move data from source to destinations, we were getting the job done. That took approximately an hour to an hour and a half when we did it with Hadoop. However, with the StreamSets, since it works on a data collector-based mechanism, it completes the same process in 15 minutes of time. Therefore, it has saved us around 45 minutes per data pipeline or table that we migrate. Thus, it reduced the data transfer, including the drift part, by 45 minutes."
"It is really easy to set up and the interface is easy to use."
"In StreamSets, everything is in one place."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"I have used Data Collector, Transformer, and Control Hub products from StreamSets. What I really like about these products is that they're very user-friendly. People who are not from a technological or core development background find it easy to get started and build data pipelines and connect to the databases. They would be comfortable like any technical person within a couple of weeks."
"Complex transformations can be easily achieved by using PowerCenter. The processing layer does transformations and other things. About 80% of my transformations can be achieved by using the middle layer. For the remaining 15% to 20% transformations, I can go in and create stored procedures in the respective databases. Mapplets is the feature through which we can reuse transformations across pipelines. Transformations and caching are the key features that we have been using frequently. Informatica PowerCenter is one of the best solutions or products in the data integration space. We have extensively used PowerCenter for integration purposes. We usually look at the best bridge solution in our architecture so that it can sustain for maybe a couple of years. Usually, we go with the solution that fits best and has proven and time-tested technology."
"The most valuable feature of Informatica PowerCenter is the flow designer functionally. It is the best out of any ETL tool. Additionally, the solution is reliable and trustable in dealing with large data sources anytime. When we're using billions of data transactions, it's smooth."
"It provides everything I need. Nothing is missing. PowerCenter is a good tool for on-premise databases."
"We have found the PowerCenter and B2B data transformation most valuable."
"It's a complete package, which is why we use this solution."
"One of the most valuable features for us is the metadata repository because it can easily understand the lineage of first target mapping. My company and I also find Informatica really easy to use—when a consultant joins our company, in just a few days to a few weeks, they can understand how to use it—so we prefer to use this ETL tool."
"It has a Data Catalog that uses the Model repository."
"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."
"I have found it to be a very good, stable, and strong product."
"Qlik Compose is good enough. It is user-friendly and intuitive."
"The logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back."
"It should be more cloud-centric than on-prem-centric."
"Support could be better."
"Its scalability can be improved. It is not scalable."
"There is some room for improvement in terms of pricing."
"I would like to see it be able to import data from NoSQL."
"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."
"PowerCenter has three clients. I wish they would consolidate everything into one GUI, not three. Also, we had a persistent issue with the Informatica Developer tool but it was solved when we migrated to the newest one."
"In the future, I would like to see Informatica PowerCenter integrate a more powerful dashboard."
"I believe that visual data flow management and the transformation function should be improved."
"For more complex work, we are not using Qlik Compose because it cannot handle very high volumes at the moment. It needs the same batching capabilities that other ETL tools have. We can't batch the data into small chunks when transforming large amounts of data. It tries to do everything in one shot and that's where it fails."
Informatica PowerCenter is ranked 1st in Data Integration Tools with 32 reviews while Qlik Compose is ranked 41st in Data Integration Tools with 2 reviews. Informatica PowerCenter is rated 8.0, while Qlik Compose is rated 6.0. The top reviewer of Informatica PowerCenter writes "A stable, scalable, and mature solution for complex transformations and data integration". On the other hand, the top reviewer of Qlik Compose writes "It's an intuitive solution for doing basic transformations, but it cannot handle high volumes". Informatica PowerCenter is most compared with Informatica Cloud Data Integration, Azure Data Factory, SSIS, AWS Glue and Informatica PowerExchange, whereas Qlik Compose is most compared with Qlik Replicate, Talend Open Studio, WhereScape RED, Palantir Foundry and Alteryx Designer. See our Informatica PowerCenter vs. Qlik Compose report.
See our list of best Data Integration Tools vendors and best Cloud Data Integration vendors.
We monitor all Data Integration Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
