We also looked at MuleSoft. I evaluated multiple solutions to determine that we would go with the choice that we chose, however, did not have experience with competitive products beforehand. Our platform was not using one.

Azure APIM is the one option we evaluated.

We did look at other options, however, this solution was more fitting for the purpose that we had.

We evaluated three different products, including API management from Apigee, API management from CA, and MuleSoft. This evaluation was three years ago, and at that time the Apigee platform was more mature than other platforms.

We also use Amazon.

We already have Apigee in our system, but we're trying to evaluate APM based on the differences between Apigee and APM.

Right now, I don't have any experience with Apigee. The only task I've been assigned is to evaluate the APIM. So far, I've only explored APIM. And all I'm doing is defining the features and differences between Apigee and APM.

We looked at a couple of other vendors. We looked at offerings by Red Hat and some others. We basically looked at the market leaders.

From an enterprise point of view, our digital division had already migrated to GCP. GCP uses Apigee by default. They had selected Apigee initially. That was one factor in choosing Apigee over CA. Another factor is that it would support on-premises and it would support our Azure environment as well. The ease of use, creation of the policy, and the developer portal experience were all factors. The fact that developers could easily create the policies themselves without having to get our administration staff or engineers to actually create the policies was a big factor as well.

We are currently looking into other solutions. We want to see how others stack up in terms of pricing, stability, scalability, et cetera. 

Previously, I had used IBM Data Power.

There is one main reason we went with Apigee and that is the importance of the Gartner and Forester ratings. Apigee is on top of all the Gartner and Forrester ratings. The other reason is because of the smooth operational perspective.

We did not evaluate other products before choosing this solution. 

We evaluated API management solutions from Oracle, IBM. Most of the solutions are similar in terms of functionality. We went for Apigee because it had more points or better ratings as per Gartner and Forrester.

We tried Axway API gateway and we also tried MuleSoft. We found that these solutions did not fit our scenario as well as Apigee because our scenario is a very special scenario where we want to keep everything that we already have on board. In our current situation, we have big AWS (Amazon Web Services) accounts and a big AWS footprint. So we want to also be able to use AWS for Apigee hosting. That is where our environment and needs become a little bit of a custom scenario. Apigee works for us in this scenario and that is why we ultimately went with Apigee over other products.  

I evaluated IBM API Connect.

If the budget is not a concern then I will choose to go with Apigee over WSA-2, but if it is then I would prefer the latter solution. Apigee is quite pricey. The price is a thorny issue as there is little room for negotiations.

Unlike WSA, Apigee does not have a partnership model, something which makes it a bit easier for companies such as ours to go with the former solution.

Apigee has better scalability than WSA. 

The company started evaluating solutions and we found that we have three other options. One of them was Mashery, the other one I don't remember the name, and the last one was SAP. The company decided to go for Apigee and now there are no plans to go to something else because the process that we take to evaluate and assess the solution is a very thorough process. We try to spend as much time as possible evaluating the pros and cons of the solutions and what issues might come up.

I have evaluated Mulesoft and Boomi. I have found these two solutions are being used secondarily to Apigee. Additionally, AWS and Azure's Gateways are becoming popular in the market. From the cost perspective, in the two years, AWS gateway is widely being used. These four solutions are widely being used in the market but Apigee is much far ahead than all other tools.

AWS and Apigee have similar features. I don't see any significant change in the difference at the moment. The choice is more about convenience and cost.

All these technologies are using Google Cloud for hosting our microservices, and we trialed Apigee. We were also using WSO2, an open-source API management tool, but as everything is on Google Cloud, we chose Apigee.

We had evaluated Software AG at the same time as Apigee. The initial setup cost for an on-premises deployment of Software AG is less than that of Apigee. For example, if I require four cores to operate Apigee then it would be a two-core system for Software AG.

We chose Apigee because of its high availability and disaster recovery. Google Apigee uses ZooKeeper with an unstructured Cassandra database. This is different from Software AG, which uses a structured database like Oracle. Having to purchase Oracle licenses increases the cost.

If you compare this to Microsoft Azure API Management, Apigee is a bit better because Microsoft has no real built-in solution.

Yes. Analysed features like pricing, support, functionality, background analysis in market, cloud connectivity, etc.

I did evaluate other options.

Yes. AWS API, 3Scale, and CA Layer 7.