IBM recently announced the deprecation of its Cloud API Gateway, a service used to create and manage APIs by placing a gateway in front of existing IBM Cloud endpoints. With this move, IBM Cloud Functions and IBM Cloud Foundry are no longer able to use Cloud API Gateway service for rate limiting, splitting, and authentication.
IBM [recommends](https://www.ibm.com/cloud/blog/announcements/api-gateway-migration-options-for-ibm-cloud-function-users)recommends several options to customers for migrating their API Gateway endpoints — among them is Kong. Although IBM mentions the open source version of Kong as a third-party solution, those running mission-critical applications and services on IBM Cloud API Gateway will be better off considering [Kong Enterprise](https://konghq.com/products/api-gateway-platform)Kong Enterprise, which extends Kong Gateway with enterprise plugins, developer portal, analytics, advanced security features, GUI, and 24/7 support.
Customers migrating from IBM Cloud API Gateway to Kong have options available to them.
Whether you select Kong Enterprise or Kong Konnect, the first thing you’ll notice is the blazing speed of the Kong Gateway that is at the foundation of both solutions.
Kong Enterprise is based on a lightweight gateway known for its ability to process thousands of transactions per second at sub-millisecond processing latency with minimal memory usage and reverse proxy with caching.
Kong Gateway utilizes NGINX as the underlying proxy technology to accept incoming requests and manage the input/output of the request/response lifecycle. NGINX is the most adopted web server in the world and processes the largest majority of traffic on the internet. With this performance, NGINX is the technology of choice not only in the cloud and for containers but also in on-prem data centers where providers are limited by rack space and server resources.
Kong has deep expertise in the full stack of Kong Gateway, including the NGINX core, which is regularly expanded by Kong with features and capabilities not natively available and has contributed to upstream NGINX. NGINX provides Kong with the fastest, most lightweight, and most reliable core engine for managing requests that Kong can freely manipulate to provide advanced API connectivity capabilities via Kong Core and its plugins.
If your current and future digital transformation plans involve operating applications and services on multiple or hybrid cloud environments, Kong offers the architectural freedom to run your applications and services in the environment and protocol of your choice.
Kong is truly infrastructure agnostic as it can be deployed across any platform (public clouds, hybrid, containers, Kubernetes), protocol (REST, gRPC, WebSockets, GraphQL, Kafka, TCP, and UDP), or architecture (monolith, microservices, serverless, service mesh, etc.) to expose, protect, and secure services consistently regardless of where they’re deployed.
Another unique architectural feature that you will experience with Kong is its industry-leading [ecosystem](https://docs.konghq.com/hub/?_ga=2.144102716.845414114.1670109132-1918615875.1667086199)ecosystem of Enterprise and community plugins.
Plugins keep the underlying API gateway core lightweight, fast, and modular by delivering API management functionality such as traffic control, security, authentication, logging, observability, and much more.
Plugins make Kong Gateway highly customizable and easy to use as you can add, configure, and remove a plugin via Kong Manager UI, Admin API call, or declaratively via Kong decK. They also provide their own configuration schema, which is automatically validated by the core and can extend the functionality of Kong quite significantly.
Kong also provides developers the ability to expand its native functionality by building new plugins using our SDK. Plugins can be built with Lua, Go, Python, Ruby, Javascript, and WasmX.
By migrating to Kong you’ll be able to take advantage of the most comprehensive plugin ecosystem that currently stands at over 100 plugins available to our Enterprise customers with new plugins being added regularly, like the ones rolled out with [Kong Enterprise 3.1](https://konghq.com/blog/kong-enterprise-3-1)Kong Enterprise 3.1.
Kong also provides your Central Enablement Team with robust API governance capabilities through a single source of truth for all the technical APIs in the organization regardless of which line of business they belong to.
Kong’s Service Hub is a permission-based centralized location for the whole organization to use as the API catalog to quickly search, discover, and consume existing services while providing a more consistent end-user experience across the organization’s applications.
Now that you have some idea about Kong’s cloud native API platform, let’s talk about our approach to migrating customers to our stack.
Our methodology involves:
This approach allows later stages of the migration to move faster with a lower overall effort as we’ve already migrated elements that have a high reusability across the ecosystem earlier in the project. Kong’s overall approach to migrating customers to our platform is outlined in the graphic below.
Kong Enterprise and Kong Konnect represent ideal choices for organizations in need of an API gateway. With full dynamic configuration, a RESTful API, support for Kubernetes, extensibility via plugins, a Dev Portal, analytics, and enterprise-grade support, Kong offers a seamless experience for those migrating from IBM Cloud API Gateway.
Learn more about Kong’s API management platform. [Talk to an API expert today](https://konghq.com/contact-sales)Talk to an API expert today.
Now you can find and purchase Kong Konnect through the Google Cloud Marketplace! Kong Konnect is the unified API platform that allows you to manage multiple gateways across service meshes, ingress, cloud, and Kubernetes providers no matter where t
[](https://konghq.com/blog/engineering/konnect-google-cloud-marketplace)
The Kong Gateway CI was failing intermittently (about once every 100 runs) on the ARM64 platform with a strange error: “attempt to perform arithmetic on local 'i' (a function value)”. The variable i in the context is an integer but at runtime, it w
[](https://konghq.com/blog/engineering/troubleshooting-an-intermittent-failure-on-arm64)
While JSON-based APIs are ubiquitous in the API-centric world of today, many industries adapted internet-based protocols for automated information exchange way before REST and JSON became popular. One attempt to establish a standardized protocol sui
[](https://konghq.com/blog/engineering/soap-to-json-with-kong-gateway)
API gateways and load balancers are useful tools for building modern applications. While they have some functionality overlaps, they're distinct tools with different purposes and use cases. In this article, we'll discuss the differences between API
[](https://konghq.com/blog/engineering/api-gateway-vs-load-balancer)
A critical and challenging requirement for many organizations is meeting audit and compliance obligations. The goal of compliance is to secure business processes, sensitive data, and monitor for unauthorized activities or breaches. AWS CloudTrail
[](https://konghq.com/blog/engineering/aws-cloudtrail-lake-isv-launch-partner)
As engineers and architects, we automatically build resilience into platforms as far as possible. But what about the unknown failures? What about the unknown behavior of your platform? The philosopher, Socrates, once said "You don’t know what you do
[](https://konghq.com/blog/engineering/optimize-your-api-gateway-with-chaos-engineering)
We understand that our customers need to deploy Kong in a variety of environments and with different deployment mode needs. That is why two years ago, in Kong 1.1, we introduced DB-less mode, the ability to run Kong without the need of connecting to
[](https://konghq.com/blog/engineering/new-storage-engine-for-kong-hybrid-and-db-less-deployments)