API Proxy vs. API Gateway
Fleeting- External reference: https://apifriends.com/api-security/api-proxy-vs-api-gateway/
API Proxy vs. API Gateway | Discover the differences
(API Gateway) concerns about security, availability, threats, and monitoring
— https://apifriends.com/api-security/api-proxy-vs-api-gateway/
proxy does a few things for you — it adds transport security, monitoring (SLA, performance), quotas, and access level to different APIs.
— https://apifriends.com/api-security/api-proxy-vs-api-gateway/
.” The proxy only works if you already have an API; when you exposed an API from within your organization to the proxy. It added nothing new.
— https://apifriends.com/api-security/api-proxy-vs-api-gateway/
expose these services as APIs, and that’s where the API Gateway comes in.
— https://apifriends.com/api-security/api-proxy-vs-api-gateway/
gateway provides orchestration. This allows you to take the services and stitch them together to build an API.
— https://apifriends.com/api-security/api-proxy-vs-api-gateway/
(API Gateway) need to be able to take these SOAP/XML services and transform it into REST/JSON APIs or take a REST/JSON API and transform it to SOAP/XML services.
— https://apifriends.com/api-security/api-proxy-vs-api-gateway/