Informatica’s Intelligent Cloud Services (IICS) platform is a solution for synchronizing and integrating cloud and on-premise applications. It offers prebuilt connectors and actions between applications and programs, allowing for data transformation within the program, as well as case-specific services.
Few scenarios 1. For viewing API analytics, I think it is best in the market 2. For earning money via API monetization 3. Securing API 4. Onboarding legacy APIs to provide modern REST endpoints
Informatica Cloud is a great tool for use when data must be formatted consistently. Once configured, it is very robust and reliable. It is also well-suited for an organization without a robust IT staff to maintain a full server infrastructure. It offers a cost-effective approach to high-quality data integration for even the largest organizations. Organizations without staff experienced in data analytics may find it challenging to take advantage of the more complex results of this tool.
Once the secure connection is established it’s quite easy to operate and create new jobs. The controls are simple, and we appreciate the fact there are not a lot of complex fine-tunings required. Navigation is also easy, and we enjoy the ability to open multiple tabs in the browser to work on multiple projects.
The monitoring functionality works well to help track the progress of the jobs, again, without too much complication. In a fast dev environment, speed is essential and we quickly seeing the status/progress of jobs as well as any errors if the jobs fail helps us maintain speed.
The web interface is a lot easier to interact with than the client/on-prem version. Putting much of the heavy lifting of interacting with the tool onto the shoulders of the browser makes it easier to keep multiple sessions open and get in/out quickly without having to VPN into the office.
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.
I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.
Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.
I've never had trouble getting into contact with Informatica's support for technical help. I give it a nine because it does pretty well for mid to enterprise-scale workflows.
Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSON
First, the wizard is easy to use making the learning curve for simple ETL tasks nice. Second, since Informatica is mature there are a good variety of connectors available. Finally, we have driven some fairly complex ETL solutions using only the cloud.
As a public entity it is hard to say how much ROI we can have. We have yet to create a billing and ROI plan. We are thinking of other ways to create ROI, possibly through data/service barter.
