WSO2 API Manager makes it possible for developers to both develop and manage APIs of different types. Unlike solutions which focus only on managing API proxies, WSO2 API Manager provides tools to develop APIs by integrating different systems as well. It supports a variety of API types from REST, SOAP, GraphQL, WebSockets, WebHooks, SSEs and gRPC APIs with specialized policies and governance for each different type. Being fully open source, its architecture and extensibility…
$0
per month
Pricing
Fiorano ESB
WSO2 API Manager
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Fiorano ESB
WSO2 API Manager
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Fiorano ESB
WSO2 API Manager
Features
Fiorano ESB
WSO2 API Manager
API Management
Comparison of API Management features of Product A and Product B
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.
It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?
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.
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.
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.
Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.
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.
We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.
