Apigee Edge vs Informatica PowerCenter

• Manage user access, we can allow specific access to users based on their need and even customize requests of services based on user requirements.
• Allow branding, so that SFO can maintain its look and feel but still get the support and functionalities we need from Apigee.
• Integrates well with other platforms we use.

Read full review

• Informatica has a wide range of support for databases. Pretty much every mainstream DBMS is compatible here.
• Designing ETL mappings and workflows is a very intuitive process, and takes minimal learning time and effort even for a beginner.
• Informatica's biggest strength is its sheer performance. It is unmatched in terms of handling large volumes of data.

Read full review

• Only one user can be active in a proxy at a time
• No version control
• Prohibited from using JSON.stringify on Apigee objects (tokens)
• Debugging is difficult
• Unable to rename or delete policies without bumping revision
• Why would anyone give a js policy one name, display name something else, and script a different name?
• 'Trace' limited to only 20 transactions
• UI allows users to add target servers, but users must utilize the api to turn on SSL.
• I'm sure there's more, they just aren't coming to mind right now.
• Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in.

Read full review

• One of the challenges of PowerCenter is the lack of integration between the components and functionality provided by PowerCenter. PowerCenter consists of multiple components such has the repository service, integration service, metadata service. Considerable time and resources were required to install and configure these components before PowerCenter was available for use.
• In order to connect to various data sources such as Netezza database or SAS datasets, PowerCenter requires the installation and configuration of separate plug-ins. We spent considerable time trouble-shooting and debugging problems while trying to get the various plug-ins integrated with PowerCenter and get them up and running as described in the documentation.
• PowerCenter works well with structured data. That is, it is easy to work with input and output data that is pre-defined, fixed, and unchanging. It is much more difficult to work with dynamic data in which new fields are added or removed ad-hoc or if data format changes during the data ingest process. We have not been as successful in using PowerCenter for dynamic data.
• One of the challenges of learning PowerCenter is that it is difficult to find documentation or publications that help you learn the various details about PowerCenter software. Unlike SAS Institute, Informatica does not publish books about PowerCenter. The documentation available with PowerCenter is sparse; we have learned many aspects of this technology through trial and error.

Read full review

• Unruly, difficult to maintain, unable to test, difficult to troubleshoot and debug. Every ticket that requires Apigee work increases stress and anxiety.

Read full review

• Positive - Easy to maintain processes built in Informatica Power Center.
• Positive - Rapidly build and deploy ETL data mappings.
• Positive - Develop the overall workflow process to run all ETL processes for the project.
• Negative - Informatica Power Center can be a bit expensive, so your application needs to warrant the enterprise support.

Read full review