I worked briefly with Amazon API Gateway but not as thoroughly as with Microsoft Azure API Management.

Amazon API Gateway is a much more technical solution and even less user-friendly than Microsoft Azure API Management.

I switched to Microsoft Azure API Management because the company decided to change its environment to Azure, so the obvious choice was Microsoft Azure API Management.

We used Oracle API Management. It's good for specific things, it's an open API. But Microsoft is easier, and can do anything, the world is moving towards Datatrix for all those things. That's why we use it.

I didn't know about any other API Management solution before, but I had read about the Apigee from Google. Azure is better as it's easier to use and has more features than Google.

I'm familiar with a variety of other solutions, including Mulesoft.

We were using DIS. We needed to install the run times, libraries, and install operating systems. We had to make a lot of initial preparations to get the process ready to operate. Now it is already available and ready to operate with Microsoft Azure API Management.

We used a CA solution before, and CA was sold to Broadcom and everything changed, politics and so and so. We had to disable CA platform due to the provider. We believe the same issues will not happen to Microsoft.

I have not used other similar solutions.

We used IBM ESB before Azure API Management, and we're using both now. ESB isn't the same as API Management from a technology perspective. They have distinct functions, but they can do similar things. You can view an API on IBM ESB, but you can view and expose API on Azure API Management. They solve similar problems but are not exactly the same.

We used to use Kong. 

Kong is more of an on-prem API gateway, and this one is cloud-based. And given that many customers are migrating to the cloud, it was actually one of the reasons why we're convincing the customers that we have used their APIs to migrate to the cloud. 

I have worked with other competing products, such as Apigee and AWS.

We switched to Microsoft Azure API Management because two years ago, someone in the organization decided to use this solution. I would never have made that decision.

I have had prior experience with API Gateway and Apigee.

We were using JIRA which can be enhanced by using third-party tools, this is a costly business so we shifted to the Microsoft platform, which was integrated for development as well as management. So that's a better way of doing things.

From previous experience, I know that Apigee is more flexible than Azure API.

We use Google Workspaces and our platform is on Microsoft Azure.

Previously, we were using AWS EC2 Instances, but because we are a Microsoft MSP and also took into account the Active Directory capabilities and the Azure Marketplace, we decided to shift more to Azure.

In this particular customer, they were using EDI-based transaction processing. We have been able to transform them into the API journey.

EDI technology is of the past and API is the modern technology that has been leading in the digital transformation, enabling them to have consumption across various platforms. Whether it's a cloud, on-premises, or an applied solution.

We didn't have a previous solution.

I have previously used Apigee and Mulesoft.

Our public APIs are mostly in Axway. B2C APIs are a combination of Azure and AWS. Cost is a big difference. Axway offers two solutions. One on-prem and the other option is cloud. It's not a SAS solution, they host us in AWS but we can push the costs for version upgrades. It's much more expensive than Azure or AWS.

I also used Tibco Mashery. There aren't so many differences. The biggest difference is that you can run it on-prem while you can't do that with Microsoft Azure API Management. 

We have also used Apigee and Azure API Management is not as robust.

I previously used RabbitMQ for another project. Both solutions have different approaches. One can work on-premises. On the whole, I still prefer is Azure API Management. I believe it's an easier solution set up and run.

We previously used IBM Open Shift. We switched due to the fact that the company was going to Azure and we didn't want multiple clients.

We did not use another API management solution prior to this one. We were developing applications and then moved into APIs.

I did not previously use a different solution. However, I evaluated other API gateways and shortlisted ForgeRock - OpenAM/OpenIG, because it has an IaaS option.

I knew MuleSoft Anypoint. I worked with it for two years.

It was better for the enterprise architecture to use Microsoft Azure API Management.

No previous solution used.

This is the first solution we evaluated and we chose it mainly in order to gain experience which is why we called it an experience project rather than a proof of concept project. We figured out that for our productive usage, we will select a different vendor.