2 Reviews and Ratings
33 Reviews and Ratings
See helpful people who have experience with this product
No answers on this topic
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.Incentivized
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.
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.Incentivized
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.
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.Incentivized
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.
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.Incentivized
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.
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.Incentivized
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.