UiPath Integration Service vs. WSO2 API Manager

Areas where it would be appropriate:

1. If you want a really 'deep' integration with a third party software, and you want all the control over how it interacts with your software
2. If you want a totally white-labeled solution, that is totally invisible to your customers.
3. if you care more about a well thought out/useful API, rather than a pretty UI

Areas where it is less appropriate:

1. If you want a Zapier-esque hands-off integration for YOU.
2. if you want your customers to do more of the work, pay for it/etc.
3. if you're a really small business, it could be too expensive. But it depends on your individual contract with them.

Incentivized

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

• Customer Support -- They have a knowledgeable team and are very responsive.
• Communication -- Most questions are addressed quickly
• Documentation -- The API documentation is well organized and easy to follow.

Incentivized

• API Security
• API Transformation
• API Monetization

Incentivized

• There weren't really many cons to our experience. The only slight downside was the cost but they worked with us on that to make it work.

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

MuleSoft is also a similar product to Cloud Elements, but is not available as an option in this form.

Workato and MuleSoft are competing cloud API connector platforms that perform a similar function to Cloud Elements. We chose Cloud Elements over them because CE provided a more robust path to unifying the behavior of connected systems.

Zapier is a workflow automation tool that I feel draws erroneous comparison to Cloud Elements that I need to highlight. Workflow automation tools (Zapier, IFTTT, Microsoft Flow) do provide multiple integrations, but for simplistic scenarios where only a handful of explicitly described steps need accomplished. Cloud Elements is a platform for developers to deliver faster and with higher reliability than making integrations one-by-one in complex systems that solve demanding problems.

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

• We are able to build integrations in HALF the time we could build them from scratch.
• They allow our development team to spend more hours focused on developing our core product, not connections to other products.
• Their large catalog of services to connect to allows us to spend much less time researching other platform integration endpoints and increases our R&D speed a considerable amount.

Incentivized

• Positive impact on continuity and API standardization.

Incentivized