What advice do you have for others considering Microsoft Azure API Management?

I would recommend Microsoft Azure API Management to others. It's cost-effective for medium to small-scale organizations that do not need a global presence. However, larger global organizations might find better alternatives. I'd rate the solution seven out of ten.

Azure API Management is better suited for enterprises due to its extensive toolset and roadmap for data integration and scalability. For smaller companies, lightweight alternatives like WSO2 are recommended. I'd rate the solution seven out of ten.

I would recommend Microsoft Azure API Management to those on the Microsoft platform. If not on Azure, consider looking into Kong. I'd rate the solution eight out of ten.

Azure API Management is a great tool to understand and use. It offers high scalability, availability, and performance. I recommend it to anyone needing a robust API management solution.

Users should create a design plan and think about splitting responsibilities to keep the service less complex. Overly complex configurations can become difficult to manage. There are many tools and libraries available, but official methods should be followed to avoid added complications. Keeping the setup simple will reduce the complexity and make it easier to manage.

There are around ten key security characteristics I look for in a solution. On the surface, my analysis so far seems to indicate that Microsoft Azure API Management has the ability to deliver on those parameters. Given the close relationship between Microsoft and OpenAI, we hope the solution will evolve more quickly and incorporate AI more fully, but we don't know for sure. Our goal is to create a composable financial institution. We are trying to get developers not to be the bottleneck anymore but to be more agile, to grow market share, and to grow national reach. To do all those things, you need very agile, world-class APIs. There are ways to make both work for that. We'll have to evaluate which one is the shorter path. I would recommend the solution for cloud-native Microsoft .NET shops with simple API requirements. However, I would not recommend it for multi-cloud, larger shops with more diverse or complicated use cases. Overall, I rate the solution a six out of ten.

We use the platform for all acquisitions and system management, automating various processes. Our API server is integrated into our cloud system ensuring everything is documented in a single query. I rate it a ten out of ten.

The availing of API protection features depends upon the customer requirements of our organization. If customers want the API to be secure and restrict accessibility then a subscription model is often integrated into the API where users will gain access to certain services upon payment. If a customer will be dealing with sensitive data through their API, then only a few individuals will have access which is implemented through Microsoft Azure API Management. I would overall rate the product an eight out of ten. I would advise others to check the documentation first as it allows you to test the product even before purchasing. Superior technical experts are not needed to operate Microsoft Azure API Management. It's an excellent learning product as one doesn't need to buy a license to start using Microsoft Azure API Management.

Microsoft Azure API Management is a good, comprehensive solution for enterprise implementation. Therefore, big organizations should definitely consider using it. Overall, I rate the solution an 8 out of 10.

Overall, I would rate the solution an eight out of ten. It's great for organizations, they can adapt. But again, it's case-by-case. The co-pilot from Microsoft is fantastic. We use that, and they went for the 300 languages and offer fantastic API. It is value for money.

Microsoft Azure API Management is a cloud-based solution. Microsoft Azure API Management is a flexible, scalable, and easy-to-use solution. Overall, I rate Microsoft Azure API Management an eight out of ten.

Overall, I would rate the solution a seven out of ten.

I rate the overall solution a nine out of ten.

I rate Microsoft Azure API Management an eight out of ten.

The solution has provided us with a great overall solution in many areas, such as security, deployment, and integrations. I rate Microsoft Azure API Management a nine out of ten.

I would rate the product an eight out of ten.

Overall, I would rate it eight out of ten. The reason is, as I mentioned earlier, it is best suited for our use case. One reason is that the product is only available in Azure. So, we are leveraging multiple managed services and building the product around that. Additionally, we select it according to the customer's needs. The hosting API workflow needs to be improved.

I'm not sure which version of the solution we're using. People should explore API management. You do get full control of your API, and from a security standpoint, you have a good understanding of the touchpoints and far more control of your traffic. You know who is accessing your services. Even if a company has legacy systems, it should have an API gateway in front of its legacy systems. We went with Microsoft since we were Microsoft partners. I'd rate the solution eight out of ten.

I would rate Microsoft Azure API Management a seven out of ten.

We use Azure and it suits our case pretty well. It could be better, but we might also have to learn more. Currently, I would rate it at an eight out of ten for our use case. We might also want to use it in the future to sell subscriptions, which is not possible out of the box. You can configure subscriptions, yet you still have to do the whole selling and measuring and things like that. That's not fully integrated.

The solution's support is very good. I rate the solution an eight out of ten.

I'm using Microsoft Azure API Management, though I've stopped active development. I'm just a user of the solution at the moment. As Microsoft Azure API Management is a cloud tool, it's automatically updated, so I'm always using its latest version. The solution doesn't require any maintenance. Seven people used Microsoft Azure API Management within the company in the past: me, the development team, and the production team. Right now, there's reduced usage, with two to three actively developing Microsoft Azure API Management, then one that handles the maintenance by checking to see if the solution still works, and that's it. I advise anyone looking into implementing Microsoft Azure API Management to invest time in learning the functionality. It takes around a month to invest, plus a good developer, so you can understand all the quirks and functionality the tool can provide, which is quite a lot. Once you have the knowledge or understanding, you can add much value to the development and integration process through Microsoft Azure API Management. My rating for Microsoft Azure API Management is nine out of ten. My company is a customer of Microsoft Azure API Management.

There are a lot of competitors in the market that provide the same kind of services but I think cost-wise and resource-wise, Microsoft is ahead and I recommend this product to our customers. That said, there are some functions we don't currently have. It's okay for a mid-size organization but for larger-scale deployments, it's lacking in some areas. As a result, I rate this solution eight out of 10.

I would rate API Management nine out of ten.

I would tell potential users to go for it. It's a good platform. Even though the ecosystem may not be that strong, it's a better option for a software development company. You can explore other options to save some bucks if you are not into software development. However, for an IT company, Microsoft Azure is the better option. On a scale from one to ten, I would give Microsoft Azure API Management an eight.

Microsoft Azure API Management is used by over a hundred development teams for developing solutions, including integrations. Currently, there's no plan to increase its usage. I would recommend the solution to other people who want to start using it. I would rate Microsoft Azure API Management eight out of ten.

I would advise others to evaluate their volumes, nonfunctional requirements, and just check whether the NFR performance metrics of API Management has been met. Otherwise, better take a trade-off between, because we have gone through the hard path, tried everything using it, and then we have moved from API Management to Apigee. I would rate this solution a seven out of ten.

If your services are built on the cloud, I think APIM is the best tool. I would rate APIM eight out of ten.

I would recommend this solution to others. I rate Microsoft Azure API Management a seven out of ten.

We're very satisfied with Azure API Management. We've had no issues with bugs, everything runs smoothly, and the connection between the cloud and the on-premise infrastructure was good. I would rate this solution nine out of ten.

Azure is the best-priced quality solution in the market. If you have business-critical processes running over API management, I would advise installing managed services either internally or from a partner to have that very close follow-up. I rate this solution eight out of ten.

I'm a customer and an end-user. My company does not have a special business relationship with Microsoft. I'd rate the solution at a seven out of ten. While technical support and documentation are lacking, I would still recommend the product to others.

We are partners. I would rate Microsoft Azure API Management an eight out of ten.

I would recommend Microsoft Azure API Management and would rate it at eight on a scale from one to ten.

I would rate Microsoft Azure API Management eight out of ten.

I would rate this product as seven out of ten.

I would recommend this solution for some small and medium-sized projects, as it is quite easy and effective to start with. I am not sure if it is suited for large companies that have heavily loaded APIs which the solution might not be able to support. I rate Microsoft Azure API Management an eight out of ten.

I would recommend this solution to others who are interested in using it. I would rate Microsoft Azure API Management an eight out of ten.

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