101 Reviews and Ratings
1 Reviews and Ratings
APIM is useful for the standard scenarios: 1) Securing your back-end APIs - If you have a legacy back-end web service that has a basic authentication scheme, you can add some additional security by placing APIM in front, and requiring subscription keys. Leverage your existing firewall to ensure only your APIM instance can communicate with your back-end API, and you've basically added a layer of protection. 2) Lift and shift - there are always going to be clients that don't want to update their clients to use a newer API; in some cases you can make a newer API look like an older one by implementing some complex policies in APIM. You can also do the opposite, making older APIs look new, such as making an XML back-end accept both JSON and XML. 3) Centralizing your APIs - if you've acquired another company and want to make their API set look as if it's a part of the larger whole, APIM is an easy way to provide a consistent front-end interface for developers. Incentivized
Well suited for publishing internal services with very high security, protecting against attacks, and managing on-demand load. Also good for transform messages and SQL to Rest services. Not appropriate for business logic implementation.Incentivized
Easy commissioning of APIs.Great policies to control access.Easy mock services for testing.Incentivized
SOAP to Rest / Rest to SOAP web services transformation.Secure authorization and authetication (JWT, OpenIP Connect, OAuth, SAML and more). WASP Features as injection protection.Easy rule writing without coding.Incentivized
Lack of robustness is a bit of an issue. Several other providers offer more options and capabilities, but then, they are lacking in interface ease.As with anything Azure, pricing is really hard to stay on top of. I always find that you really don’t know what you’re paying for until you get the bill. Having an excellent Azure Administrator can help resolve that.Integrating with app services outside of Azure can be a challenge, or at least much more challenging than just using Azure App Services.Incentivized
It would be nice to have an integration with services like Github for managing projects and versions.Incentivized
The Layer7 API Management is a great solution, but, sometimes the documentation is not clear or has lack of examples.Incentivized
The support team is good and the response time is reasonable, but (there is always a but), when support inquiries are made by someone experienced, and the question is not trivial, it is boring and takes a long time to get the case escalated to the next level of support.Incentivized
Azure APIM vs Amazon API Gateway: 1) Azure APIM was a complete package that included a developer portal.2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway. Incentivized
We evaluated 3 tools and decided on Layer7 API Management because it had the shortest implementation times and fastest learning curve, without losing power of customization and scalability.Incentivized
We can always think of positive ROI impact on businessIt helps to easily facilitate the design, deployment, and maintenance of our APIs
Very fast implementation and is easy to learn & use.Incentivized