Flowgear vs. WSO2 API Manager

Flowgear has been exceptionally well suited to automate workflows allowing my product to interface with other products without the need for my team to develop these integration points. The ability to run workflows against multiple environments, in a secure manner, has facilitated rapid development of key client requirements and aided my team in delivering a quality solution.

WSO2 is a unique product that provides pre-integrated components like Gateway, Integrator, identity management, etc. Hence it is best suited when the requirement is not just only publish the APIs but also to secure and transform the APIs. WSO2 can be an overhead if only Gateway is required, as there are other very lightweight gateways available in the market.

Incentivized

• Easy node code front end
• Excellent Customer Service
• Adding new pre-built integrations on a regular basis

Incentivized

• API Security
• API Transformation
• API Monetization

Incentivized

• Learning should be easy for even a beginner
• Users may find the platform a bit overwhelming if they do not understand it

Incentivized

• Installation of this product is a hell. You need to be an expert to get this running together with WSO2 Analytics. It uses a really confusing method of "port + 1" to connect extra products. I guess this was meant to provide a handy way to add new WSO2 products. In reality you'll need to scroll through numerous config files to set this straight. If you use this out of the box, everything will work all right. But the moment you add SSL certificates, DNS names and you'll need special ports to configure your firewall, this product becomes unmaintainable.
• The "Store" provides a nice way to group API's. However, the "Publisher" does not... if you have more than 30 API's searching for API's becomes really annoying.
• The number of configs in this product is huge. As a developer myself, I've never seen (and definitely never created) a product that needed that much config files. Installation and maintenance of products should be stupidly simple, since no developer nor infrastructure person wants to learn something that "just" needs to be a tool.. opposed to being a whole new area of expertise. After using WSO2 API Manager for a while, we wanted to change the admin password... this should be simple enough, like just change the password in "Carbon." But nope. The whole WSO2 environment crashed. We just gave up. Too dangerous.
• Why so many different "products"? Publisher, Store, Carbon, and numerous hidden interfaces. Analytics, ESB whatever... No wonder there are so many config files and port issues. Make it simple!!!

Incentivized

Training material is excellent with in depth videos and material that are readily available and easy to understand. Materials are upgraded when new features are out. First time users do not find it difficult to follow and understand all modules. Tests are easily completed due to this. Overall training was great

Flowgear has solved our problem in getting our integration and mapping out faster. Easily being able to change workflows and great with facilitating a production ready product through its CI\CD functionalities. Taking the products through various stages of development ensures that we are always able to test extensively first and then get our integration working in a production ready environment.

Incentivized

Nevatech Sentinet: The easiest API Manager available. No knowledge of how the product works internally needed! It works with C# (not java... with all it's config files... really? Java developers?). Great way to categorize API's into groups (domains). All of which is drama in WSO2. But Sentinel is really expensive... Mulesoft: Nice and clean. Again, no expert knowledge needed of how the product works internally. Like using word... or any other application, except WSO2. Have java developers never heard of exposing configurations through a user inyterface?? Mulesoft, however is really expensive. Azure: Not cheap!! And a chaotic interface too. But it pays! If you have a Microsoft account already, this is your next step. We chose WSO2 4 years ago because it was free... but we're moving to azure now. And we're very happy with that decision.

Incentivized

• increased productivity
• efficiency
• and reduced time and costs

• Positive impact on continuity and API standardization.

Incentivized