From cca7c10d38cafce157798e95fe90bdcb5cf6d0d3 Mon Sep 17 00:00:00 2001 From: Yilia Date: Mon, 17 Feb 2025 14:24:29 +0800 Subject: [PATCH] fix typo --- .../02/17/cloud-vs-open-source-vs-commercial-api-gateways.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/en/blog/2025/02/17/cloud-vs-open-source-vs-commercial-api-gateways.md b/blog/en/blog/2025/02/17/cloud-vs-open-source-vs-commercial-api-gateways.md index daec7edd49c12..a97f422848d8e 100644 --- a/blog/en/blog/2025/02/17/cloud-vs-open-source-vs-commercial-api-gateways.md +++ b/blog/en/blog/2025/02/17/cloud-vs-open-source-vs-commercial-api-gateways.md @@ -30,7 +30,7 @@ API gateways have become essential components in modern cloud architectures. The Broadly, API gateways fall into three categories: - **Cloud API Gateways** (e.g., Amazon API Gateway, Google Apigee) -- **Open Source API Gateways** (e.g., Apache APISIX, Kong Gateway, Tyk) +- **Open Source API Gateways** (e.g., Apache APISIX, Kong API Gateway, Tyk) - **Commercial API Gateways** (e.g., MuleSoft, Boomi) Each option has its advantages and trade-offs. This article provides a deep dive into their differences, hidden risks, and a **strategic recommendation** for companies looking to scale API usage and adopt hybrid cloud architectures.