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

• Easy integration of the TIBCO Cloud Mashery developer portal allows simple onboarding and user and application management.
• Configuration of TIBCO Cloud Mashery is both flexible and focused to address the main tasks for an API Management solution.
• The built-in OAuth Token capabilities provide a quick start to properly manage application access.

Read full review

• I think there should be another way of enabling CORS. It basically creates OPTIONS for every endpoint, which makes your API Gateway look complicated.
• The integration timeout limit is 30 seconds, which limits you into that time.
• API Gateway UI should be improved and should work correctly when more than two people are adding/editing endpoints.

Read full review

• The "Control Center" admin dashboard is not performant. We have a lot of configuration data in Mashery (many endpoints, many plans, many users, many keys, etc.) and the website struggles with the volume of data it has to deal with.
• Their systems have limitations that make it more difficult for us to operate the way we would like. For example, there is a limit to the number of API Definitions we can create, as well as a limit to the number of Endpoints we can define in a Plan.
• Their support organization leaves a lot to be desired. Responses are slow, and when they do come they are often inadequate. We have to re-phrase the question to get them to answer it differently, or we have to repeatedly follow up to ask for additional clarifying information.

Read full review

• ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues.
• For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical.
• Service is easy to set up authorization and it is easy to manage.

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