Where does your reverse proxy end and API Gateway begin?

Posted by Inevitable-Basis-267@reddit | sysadmin | View on Reddit | 3 comments

Started with nginx, kept adding auth, rate limiting, custom routing on top... at what point did you just switch to a proper API Gateway?

Made a deep dive on this if curious: [https://youtu.be/-R5ak7-LiVY]

[-]

Kumorigoe@reddit

Sorry, it seems this comment or thread has violated a sub-reddit rule and has been removed by a moderator.

Do Not Conduct Marketing Operations Within This Community.

It is not acceptable to advertise a product, service, Blog or FOSS Project within this community outside of authorized threads.
It is not acceptable to perform product research or market research within this community without permission.
The Reddit advertising system exists to help you reach out to new or existing customers.
Product Representatives are free to discuss their product in the context of an existing, naturally-occurring discussion. Astroturfing is not permitted.
As always, users must disclose any affiliation with a product.
Content creators should refrain from directing this community to their own content.

Your content may be better suited for our companion sub-reddit: /r/SysAdminBlogs

If you wish to appeal this action please don't hesitate to message the moderation team.

[-]

delliott8990@reddit

In my experience, one thing that works is architecting the reverse proxy in a modular fashion with a handler stack. You can set up one for auth, rate limiting, rewriting, key validation, etc.

Having said that, I haven't watched your video yet so you may very well be aware already. Will check it out later!

[-]

6SpeedBlues@reddit

They're different tools to provide different functionality. Using the two together is quite common.