Axway's Amplify is a universal API management platform that unifies what tools are already in place to get digital products where they can be seen and used. Users can publish, validate, and govern APIs.
N/A
IBM API Management
Score 8.9 out of 10
N/A
IBM API management enables creation and management of web application programming interfaces (API).
It's a great application to backup your data automatically to the cloud and then access later. The automatic restore of certain folders is handy and one less thing to worry about when you're setting up a new PC again. I haven't really encountered any issues with Syncplicity to have any thoughts where it could be improved or where it wouldn't work.
If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.
Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy.
Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises.
API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth.
I would appreciate it if it backed up more than just Desktop, Favorites and Documents by default. I'm not sure if this was something chosen by my employer, but it would be nice if the whole profile folder was backed up by default, so my pictures, music, and videos folders were included.
Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough.
Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling.
Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement.
It offers a wide range of powerful tools for API management, data integration, B2B integration, and more. Strong security features and compliance support add significant value. Flexibility to integrate across various environments (cloud and on-premise) enhances usability for diverse infrastructures.
I use CrashPlan for my personal PC at home. I think both products have their pluses and minuses. Both products allow you to backup your selected data to the cloud. CrashPlan doesn't easily allow for file sharing (CrashPlan isn't really a collaboration tool as much as it is a backup tool). Both products have easy restore options. However Syncplicity automatically restoring certain data when syncing with a new PC is very handy and a feature that CrashPlan doesn't offer
There are a lot of similarities between Apigee Edge and IBM API Management. Some of the differences at the time of this posting is... 1) IBM APIM/C integrates better with other products. Dynatrace is used to track API and service specifics with the ability to offload those statistics for operational reporting. 2) If you are evolving from DataPower, IBM API Management is a logical choice to support additional REST APIs. 3) Generating keys is simple. Integration of those keys with a secure data vault is easy as well for your consumer.
Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used.
Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients.
Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money.