Apigee Edge vs. Boomi vs. WSO2 API Manager

Few scenarios 1. For viewing API analytics, I think it is best in the market 2. For earning money via API monetization 3. Securing API 4. Onboarding legacy APIs to provide modern REST endpoints

Incentivized

Legacy systems often need to be replaced or integrated with new applications in order to modernize businesses. A strong API strategy that avoids custom coding and third-party programs is essential to enable this integration. Boomi's new-age connectivity and integration solutions ensure safe, secure, and robust integration. In the age of information, businesses are under more pressure than ever to be able to collect and manage large amounts of data. This data comes in from a variety of sources, including personalized devices such as voice assistants and wearable tech. While this data can be immensely valuable to businesses, they often lack the infrastructure necessary to handle it effectively. This can lead to data build-up in databases or silos, and can eventually lead to problems with integration and security.

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?

Incentivized

• Better exception handling with the Raise exception policies help to monitor the flow by setting up the flow conditions.
• Easy development of a Proxy and APIs with much less tutoring and helps make getting started for new users easy.
• Very good documentation and blog with details of most common failures and error handling.
• A very very easy to use console.

Incentivized

• Pre-built connectors to almost anything which greatly reduce time to release of your integration needs.
• Easy to use development platform with drag&drop features. Non-technical people could build simple integration processes in no time.
• Great user community where you can get quick help if needed. Boomi people hang around there a lot.

Incentivized

• Authentication based on OAuth 2.0 and HTTP Basic Authentication.
• Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
• Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
• Mediation to perform transformation, orchestration etc.

Incentivized

• Only one user can be active in a proxy at a time
• No version control
• Prohibited from using JSON.stringify on Apigee objects (tokens)
• Debugging is difficult
• Unable to rename or delete policies without bumping revision
• Why would anyone give a js policy one name, display name something else, and script a different name?
• 'Trace' limited to only 20 transactions
• UI allows users to add target servers, but users must utilize the api to turn on SSL.
• I'm sure there's more, they just aren't coming to mind right now.
• Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in.

Incentivized

• More from a development perspective. It is always difficult to use the properties features. It takes a while to understand how the data/variables can be used across an integration.
• Dell Boomi should also invest more on API Management and not just seen as a ETL,ESB tool.
• Should roll out features more often based on users reviews.

Incentivized

• Better QA testing prior to releases rollout
• Better support needed

Incentivized

I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.

Incentivized

Dell Boomi has provided us with the ability to connect our campus together using our various existing platforms. There are many supported features and have yet to run into something that we cannot do. Its user interface is very intuitive which would allow users to begin developing fairly easily. There is a myriad of resources available

Incentivized

Support has helped us to resolved all the queries and community support was also good.

Incentivized

My IT and Finance teams have noted that setting up the tool is a breeze. Dell Boomi has never caused an issue during a system implementation that I am aware of. We are pleased with the tool and recommend others consider it.

Incentivized

The atom sphere takes a time to load, when I open a process or when I open a log. One more slow processing is when I import objects from NetSuite.

About the performance of processing, it looks like Boomi takes a time to initialize some things such as connectors before starting the process. This is also performance we have.

Incentivized

Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.

Incentivized

Boomi support was responsive and knowledgable, however being a closed cloud service, it doesn't have good community support. We found the learning curve to be steep and there aren't avenues like google, forums, or blogs that provide community driven insight into the product or how to go about designing solutions using the tool

Incentivized

Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSON

Incentivized

We decided to go with Dell Boomi because another department in our company was already using the software. We did not research competitor applications to use as our business solution. Dell Boomi was very easy and quick to set up, so once we decided to use Dell Boomi for systems integration, we had it set up and running within a few working days.

Incentivized

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.

Incentivized

• As a public entity it is hard to say how much ROI we can have. We have yet to create a billing and ROI plan. We are thinking of other ways to create ROI, possibly through data/service barter.

Incentivized

• It has allowed us to scale significantly without having to add headcount, specifically those geared towards data entry. We went from a $10m ARR business to $200m ARR business with the same amount of Order Processors and 12x amount of transactions by leveraging Boomi to perform a lot of the work, and then having the Order Processing team to simply review that the transaction was processed successfully.

Incentivized

• 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.

Incentivized