If you were talking to someone whose organization is considering Microsoft Azure API Management, what would you say?
How would you rate it and why? Any other tips or advice?
My advice to those wanting to implement this solution is in all technology areas, each solution is use case-specific. If you are already working on the pure Azure Stack, then APIM is something that I would suggest. Unless you have a very complicated API development use case I would not try to deploy, for example, Mulesoft or Apigee on Azure. Assuming you are working on a full Azure Stack solution. Since it is use case-specific, rather than trying to build out. I would rather use the other repertoire of Azure to do the API development, as opposed to trying to deploy other solutions under the platform and develop from there. My philosophy is always, use what is available, rather than trying to reinvent the wheel. Mulesoft may be powerful, but it is putting the cart on top of the wheel and try to build something on the cart. It is not a native approach. I rate Microsoft Azure API Management a seven out of ten.
I would advise those wanting to implement this solution that they can use this solution if it fits their deployment criteria. However, there are better options available. I rate Microsoft Azure API Management a seven out of ten.
We are Microsoft partners. I'd recommend the solution to other individuals and organizations. Overall, I've been quite satisfied with its capabilities. I'd rate the solution seven out of ten.
I would rate this solution an eight out of ten.
We're just a customer. We do plan to continue to use the product going forward. I'm not sure if I would recommend the solution. It depends on how their organization and architecture is, and if they're doing on-prem or cloud, depending on the requirement. It's very hard to say. That said, I would rate it overall at eight out of ten.
Right now, for a particular client, we're using a managed version of the solution, however, in the future, I foresee us hosting it somewhere in the cloud. We're using the most up to date version of the solution. Overall, the solution has a lot of great features. There are a few bugs here and there, however, a the end of the day, there's lots of value provided. I'd rate the solution at an eight, on a scale from one to ten. It's got a rather high cost and still has some areas that need some improvement. Otherwise, I'd rate it higher.
At the end of the day, all the products are one and the same, just that some of them have more features than others. That's all. I would rate Azure a seven out of ten. Not a ten because I would like for them to improve on the number of policies it has inbuilt and for it to have better deployment architecture.
My advice would be to choose wisely. Look around. That's the free entry stuff, so that's why I'm kind of looking around for another tooling solution, to see if I can get more full-featured support. In the next release, I would love to see them actually support out of the box, like a canary deployment pattern, or out of the box just a blue-green rolling deployment pattern. Right now, how you want to do your deployments, you've got to tool it yourself. I would rate it a seven out of ten. They're not bad.
You can't use this on-premise. If you want to run on-premise you would have to get a different product. Other than that, it's easy to use and start up. There is a lot of support available from the community online. You can do a domain name yourself with Microsoft, as opposed to other products where you need to contact support in order to set up a domain. I would rate it an eight out of ten. I can't give a ten out of ten because I'm not experienced enough with it. So far so good, though.
I would recommend doing a combination of AWS API Gateway and Azure API Management. You can authenticate APIs in Azure Active Directory and from there you expose all of your serverless components and use them as a backend with Azure. But it depends on what your use case is. It can be used as a combination or as a standalone. I would rate it an eight out of ten. To make it a ten, there should be better analytics features so we can know how our product is performing.
I would rate this product a seven out of 10.
I would rate this product a six out of 10.
So far, we've been very happy with the solution. I'd rate it eight out of ten overall.
API and microservices based architectures is the modern architecture to enable organizations for digital growth. With that said Microsoft Azure is definitely is in the top quadrant in this space and are investing to grow this service portfolio by leaps and bounds every day. Based on our customer ecosystem and the predominant technology stack in use, the decision with Microsoft platform aligns well with their transformation roadmap. There is going to be some level of Microsoft cloud solutions in play. Each customer has to conduct an assessment on the need for a platform based on the technical debt they are carrying along with people and process. They need to take a look at the existing ecosystem, software technology stack, current ERP, and the applications that need to be integrated into API based platforms. I would suggest Azure API Manager should be in your selection process. I would rate this solution a nine out of ten.
This is absolutely a solution that I would recommend for others. I would rate this solution a nine out of ten.
We do not use one particular feature over another. Rather, it is the whole package that is useful. I would rate this solution a six out of ten.
Approach API Management in the two areas "tooling" and "governance". Tooling required end-to-end thinking from a developer, consumer and infrastructure perspective. For each multiple examples can be shared. For governance start with the obvious fitting to your organization. Do not follow all recommendations from the start, hence expect an iterative approach. I would recommend this product and would rate it an eight out of 10.
I would recommend this solution to someone considering it. I would rate it a nine out of ten.
Which solution is preferable?