Likelihood to Recommend Fiorano would be a good choice for small-medium businesses that need integration capabilities with clients but don't want to carry the burden of an in-house development team. The software can be used by technical non-developers and the organization offers professional services to get you off the ground. For larger organizations that have an in-house development team and a wealth of internal resources, other "enterprise grade" middleware/ESB solutions may be more applicable.
Read full review 1.- Scenaries with poor sources of data is not recomended (Very bad ROI). The solution is for medium-big enterprises with a lot of sources of data and users. 2.- Bank and finance enviroment to integrate differente data form trading, Regulatory reports, decisions makers, fraud and financial crimes because in this kind of scenary the quality of data is the base of the business. 3.- Departments of development and test of applications in enterprises because you can design enviroments, out of the production systems, to development and test the new API's or updateds made.
Read full review Pros Fioranio's underlying design is very good. In the event of a sudden shutdown, it would - in theory - be able to recover messages that were in-flight. The visual design surface is very appealing and provides a very quick and easy way to decipher data flows. It has a definite advantage over traditional develop and document processes where documentation tends to be out of date. With Fiorano, the flow is already visualized in a relatively easy to understand way. One thing that Fiorano had over some competitors was connections into our AS400 data queues. Not all middleware solutions have that - which is a boon for organizations that still run an iSeries in the back-end. The support people are generally very well educated and easy to get a hold of if you have a support agreement in place. Read full review Informatica Powercenter is an innovative software that works with ETL-type data integration. Connectivity to almost all the database systems. Great documentation and customer support. It has a various solution to address data quality issues. data masking, data virtualization. It has various supporting tools or MDM, IDQ, Analyst, BigData which can be used to analyze data and correct it. Read full review Cons Fiorano scalability was a problem for us - specifically we were told about a limit of the number of components that could be run on a single server. This was not explained during the pre-sales and is a serious limitation of the platform. Some of the components in Fiorano are just poorly implemented. For instance, we used the FTP component to download a large multi-GB file. Apparently, that component requires equal RAM to file size. So, if you download a 10GB file, you'll need at least 10GB of RAM to do so. Stability was also problematic for us - some of the components or entire data flows would suddenly stop for no reason. At time they coudln't even be restarted and we were forced to restart the Fiorano service. Not an ideal situation to be in for mission critical data flows. Consistency is a problem for the components in Fiorano. There are wide ranges of design variations in the UI between components. Even in the same component, it could be the case that you'd have to switch back to the "old" component UI to view certain important settings. This made development more difficult. 3rd party support doesn't exist - perhaps it isn't popular enough? There isn't a community supporting Fiorano which means that problems require you to go to a support person. Read full review There are too many ways to perform the same or similar functions which in turn makes it challenging to trace what a workflow is doing and at which point (ex. sessions can be designed as static or re-usable and the override can occur at the session or workflow, or both which can be counter productive and confusing when troubleshooting). The power in structured design is a double edged sword. Simple tasks for a POC can become cumbersome. Ex. if you want to move some data to test a process, you first have to create your sources by importing them which means an ODBC connection or similar will need to be configured, you in turn have to develop your targets and all of the essential building blocks before being able to begin actual development. While I am on sources and targets, I think of a table definition as just that and find it counter intuitive to have to design a table as both a source and target and manage them as different objects. It would be more intuitive to have a table definition and its source/target properties defined by where you drag and drop it in the mapping. There are no checkpoints or data viewer type functions without designing an entire mapping and workflow. If you would like to simply run a job up to a point and check the throughput, an entire mapping needs to be completed and you would workaround this by creating a flat file target. Read full review Likelihood to Renew Our team enjoys using Informatica and feels that it is one of the best ETL tools on the market.
Read full review Usability Positives; - Multi User Development Environment - Speed of transformation - Seamless integration between other Informatica products. Negatives; - There should be less windows to maintain developers' focus while using. You probably need 2 big monitors when you start development with Informatica Power Center. - Oracle Analytical functions should be natively used. - E-LT support as well as ETL support.
Gurcan Orhan Data Quality Management Software Development Manager
Read full review Performance PowerCenter is robust and fast, and it does a great job meeting all the needs, not just the most commercially vocal needs. In the hands of an expert power user, you can accomplish almost anything with your data. It is not for new users or intermittent users-- for that the Cloud version is a better fit. Be prepared for costly connectors (priced differently for each source or destination you are working with), and just be planful of your projects so you are not paying for connectors you no longer need or want
Read full review Support Rating Informatica power center is a leader of the pack of ETL tools and has some great abilities that make it stand out from other ETL tools. It has been a great partner to its clients over a long time so it's definitely dependable. With all the great things about Informatica, it has a bit of tech burden that should be addressed to make it more nimble, reduce the learning curve for new developers, provide better connectivity with visualization tools.
Read full review Alternatives Considered We are evaluating options such as Apache Nifi as a possible replacement for our Fiorano data flows. We've also used PilotFish technologies that has been able to fit the same use cases as Fiorano (minus the visual component). Generally the products mentioned above excelled in areas of stability and through-put compared to Fiorano, but none have been able to consolidate our ESB components into a single platform.
Read full review While
Talend offers a much more comfortable interface to work with, Informatica's forte is performance. And on that front, Informatica Enterprise Data Integration certainly leaves
Talend in the dust. For a more back-end-centric use case, Informatica is certainly the ETL tool of choice. On the other hand, if business users would be using the tool, then
Talend would be the preferred tool.
Read full review Return on Investment Fiorano added another piece of complexity to our ESB solution but has not pulled its weight as far as ROI. As we started ramping up on the product, it continued to show it's short-comings and we are working now to ramp it down. Overall, it has not been a positive experience. Read full review The data pipeline automation capability of Informatica means that few resources are needed to pre-process the data that ultimately resides in a Data Warehouse. Once a workflow is implemented, manual intervention is not needed. PowerCenter did require more resources and time for installation and configuration than was expected/planned for. The lack of or minimal support of unstructured data means that newer sources of dynamic/changing data cannot be easily processed/transformed through PowerCenter workflows. Read full review ScreenShots