We performed a comparison between Informatica PowerCenter, Pentaho Data Integration and Analytics, and TIBCO Scribe based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."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."
"I like the automated scheduling feature."
"The number of docs has been reduced drastically, which is very good."
"It provides monitoring and we can therefore be aware of what is happening when we are handling jobs."
"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."
"Informatica PowerCenter is a very good ETL tool."
"Among all the solutions I have used, I found Informatica PowerCenter to be much more stable in terms of application."
"Enterprise-scale ETL solution that's very stable and is easy to scale. It integrates and connects with multiple new systems, both structured and semi-structured."
"The amount of data that it loads and processes is good."
"I absolutely love Hitachi. I'm one of the forefront supporters of Hitachi for my firm. It's so easy to integrate within our environments. In terms of being able to quickly build ETL jobs, transform, and then automate them, it's really easy to integrate throughout for data analytics."
"The graphical nature of the development interface is most useful because we've got people with quite mixed skills in the team. We've got some very junior, apprentice-level people, and we've got support analysts who don't have an IT background. It allows us to have quite complicated data flows and embed logic in them. Rather than having to troll through lines and lines of code and try and work out what it's doing, you get a visual representation, which makes it quite easy for people with mixed skills to support and maintain the product. That's one side of it."
"This solution allows us to create pipelines using a minimal amount of custom coding."
"It has improved our data integration capabilities."
"Pentaho Data Integration is quite simple to learn, and there is a lot of information available online."
"Data transformation within Pentaho is a nice feature that they have and that I value."
"I can use Python, which is open-source, and I can run other scripts, including Linux scripts. It's user-friendly for running any object-based language. That's a very important feature because we live in a world of open-source."
"The most valuable feature of TIBCO Scribe is the connectors available to various products."
"We had to take on a large volume of data from the legacy Sybase system. This was taking a very long time, i.e., more than a day. We were trying to improve it with partitions to gpload, but we were told that we can't go more than four partitions."
"What I didn't like about it is that the platform itself is not great at distributed processing. When you need high parallel processing, it has some inherent issues. We had to use Java transformation, and it did not go very well. I have heard that it is going to the cloud, but we haven't tried that."
"Requires an established data center because there is no option for software as a service."
"The price of the product is an area of concern where improvements are required, considering the fact that the present licensing charges of the tool are expensive."
"What needs improvement in Informatica PowerCenter is the cloud experience because, nowadays, other companies, such as AWS, Azure, and Google, have more experience in the cloud. The pricing for Informatica PowerCenter on the cloud is also very expensive for customers, so some customers prefer open-source tools or lower-priced tools, such as Azure. From my point of view, Informatica must work on the pricing policy and review the policy on the cloud for Informatica PowerCenter or propose more tools with lower pricing. Clients want the automatic integration of Informatica PowerCenter with other tools. Currently, the integration process is manual, and you have to add other tools to facilitate the integration, especially with the DevOps methodology. You need scripts and tools for the integration, and you'll need to use other integration tools if you want automatic deployment for Informatica PowerCenter, so this is another area for improvement in the solution. What I'd like to see in the next release of the solution is for the integration with APIs to be simpler, because currently, the API integration feature of Informatica PowerCenter is very difficult. It's not intuitive. You have to facilitate API integration and the real-time streaming of messages in Kafka, for example, so that should be improved."
"Its licensing can be improved. It should be features-wise and not bundle-wise. A bundle will definitely be costly. In addition, we might use one or two features. That's why the pricing model should be based on the features. The model should be flexible enough based on the features. Their support should also be more responsive to premium customers."
"The real-time database connectivity when getting the real-time data using the VPN is an area that needs improvement."
"Areas for improvement in Informatica PowerCenter include scalability and high availability or the clustering configuration because that's still very basic. The elasticity or scaling of the platform needs a lot of improvement. For example, when it comes to DR handling or building an active-active or active-passive cluster, Informatica PowerCenter is still not that powerful. Automation also needs improvement in the solution. Improving automation leads to some improvement in the stability of Informatica PowerCenter and other aspects related to it. What I'd like to see in the next release of Informatica PowerCenter is real-time capability because the solution is mainly for patches, and to have real-time integration, you need to count on some additional components from Informatica. I would expect more integration and a complete platform in terms of real-time capability or patching with minimal interventions or minimal components to be aligned together."
"Parallel execution could be better in Pentaho. It's very simple but I don't think it works well."
"I work with different databases. I would like to work with more connectors to new databases, e.g., DynamoDB and MariaDB, and new cloud solutions, e.g., AWS, Azure, and GCP. If they had these connectors, that would be great. They could improve by building new connectors. If you have native connections to different databases, then you can make instructions more efficient and in a more natural way. You don't have to write any scripts to use that connector."
"I was not happy with the Pentaho Report Designer because of the way it was set up. There was a zone and, under it, another zone, and under that another one, and under that another one. There were a lot of levels and places inside the report, and it was a little bit complicated. You have to search all these different places using a mouse, clicking everywhere... each report is coded in a binary file... You cannot search with a text search tool..."
"In the Community edition, it would be nice to have more modules that allow you to code directly within the application. It could have R or Python completely integrated into it, but this could also be because I'm using an older version."
"Some of the scheduling features about Lumada drive me buggy. The one issue that always drives me up the wall is when Daylight Savings Time changes. It doesn't take that into account elegantly. Every time it changes, I have to do something. It's not a big deal, but it's annoying."
"A big problem after deploying something that we do in Lumada is with Git. You get a binary file to do a code review. So, if you need to do a review, you have to take pictures of the screen to show each step. That is the biggest bug if you are using Git."
"I would like to see improvements made for real-time data processing."
"I would like to see improvement when it comes to integrating structured data with text data or anything that is unstructured. Sometimes we get all kinds of different files that we need to integrate into the warehouse."
"The solution should provide better documentation and scenario-based samples."
More Pentaho Data Integration and Analytics Pricing and Cost Advice →
