Using Amazon API Gateway as a Wrapper for Another API – Thoughts?

Hey everyone,
I'm considering using Amazon API Gateway as a wrapper around an external payment API. The primary reason is to abstract away the details of the underlying API and add an additional layer of control and security. Before diving in, I wanted to gather some insights from the community.
So I'm acting as an intermediary between a client and a partner. The client needs to make payments using the partner's API. A bussiness restriction is that the client cannot directly interact with the partner's API, so I'm thinking of creating a wrapper around it, but would prefer avoid having to develop software just to abstract all the endpoints into my own and turning it into a possible point of failure. Also, I need to manage my own authentication and authorization for the client.
From my research, Amazon API Gateway seems to fit the bill, offering integration requests, transformation templates, built-in security features, and integration with CloudWatch for monitoring.
Has anyone here used Amazon API Gateway in a similar manner? I'd love to hear about your experiences, potential pitfalls, and any alternative suggestions.
Thanks!

submitted by /u/antoninu_
[link] [comments]

from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/MpQR96L

Leave a comment

Design a site like this with WordPress.com
Get started
search previous next tag category expand menu location phone mail time cart zoom edit close