Amazon API Gateway vs TIBCO Cloud Mashery

• API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
• API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
• API Gateway's pricing can be very attractive for services that are accessed infrequently.

Read full review

• TIBCO Mashery is a very stable platform. We run on-premise version without any major outages for more than 1.5 years.
• Hybrid deployment model of Mashery is a big plus. Traffic can be routed through local gateways or through gateways hosted on Mashery cloud.
• Mashery allows combining multiple API into packages which can be consumed by different applications. Even multiple API's can be combined into the single package and consumed by single API credentials.
• Mashery organizational model is exceptional. It allows us to limit users to manage just their API's within suborganizations. It's great as multiple DevOps teams can independently manage API by themselves without talking to central API team and it keeps them in boundary of their suborganization.

Read full review

• API Gateway introduces some concepts, such as Stages and Integration Requests, that are foreign to most developers. The documentation hints in the Console help, but sometimes these concepts are not transferred to frameworks like Serverless.
• Systems that use API Gateway may behave differently in end-to-end tests in local or CI environments.
• Navigating the Console can be confusing.
• It could be easier to codify API Gateway configurations.

Read full review

• The API technology is advancing fast. Capability enhancements for message-driven APIs are not yet available in TIBCO Cloud Mashery.
• While TIBCO Cloud Mashery features OAuth Token capabilities, integration with major OAuth and OpenID Providers is not straight forward.
• TIBCO has enhanced the features on managing the platform using TIBCO APIs. Still, not all features are provided as APIs and require manual configuration in management portal.

Read full review

• API Gateway has positively impacted our business by increasing the stability of our services. It is easy to implement rate limiting and horizontal scaling with API Gateway; this helps us to deliver highly-available services.
• API Gateway has increased our developer's productivity because they can delegate the management of web services to AWS. They can focus on features instead of Nginx configurations.
• API Gateway makes access control easy, which makes securing our services easier.

Read full review

• As a API Mediation layer it has helped with the troublesome port setup with internal and external clients. Meaning it made that easy to the client that they know where to go for access to an API.
• The interactive documentation is very well put together and has reduced the time that developers have to go back and forth with each other to figure how to call the API.

Read full review