Why Layer7 is good when starting and still good when it's largely adopted.
August 14, 2019
Why Layer7 is good when starting and still good when it's largely adopted.
Score 9 out of 10
Vetted Review
Overall Satisfaction with Layer7 API Management (formerly CA API Management)
We are mainly using Layer7 API Management as a security gateway. Our customers are able to expose internet legacy and internal services to a new partners, delegating the authentication, authorization, data transformation, analytics and security controls to Layer7 practically without modifying their current software. It is used as a OAuth server or as a point for identity verification.
- 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.
- It would be nice to have an integration with services like Github for managing projects and versions.
- Very fast implementation and is easy to learn & use.
- Apigee Edge and Mule ESB
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.
Layer7 API Management Feature Ratings
Using Layer7 API Management (formerly CA API Management)
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Well integrated Consistent Quick to learn Convenient Feel confident using | None |
- Publishing Swagger documented services.
- SQL to RESTful services.
- Granularity of permissions within the developers team.
- Build and automate migration of policies between DEV->QA>PROD. You need to be very careful about how to make the rules for transparent promotion from one environment to another.