2/12/2024 0 Comments Maven virtual gateway![]() Unlike many traditional API management vendors, being an independent offering from any of the public cloud vendors allows Kong to be truly cloud-agnostic. With traditional API management platforms like Apigee, we’ve seen customers who simply couldn’t achieve this degree of deployment control, severely jeopardizing their infrastructure journey. We allow customers to first deploy onto bare metal, virtual machines, Docker and then take that same runtime and deploy it on their preferred distribution of Kubernetes on-prem and across one or more clouds. Kong provides unbeatable flexibility to support this journey. Most commonly, this means starting on-prem, then moving to the cloud, and then on towards multi-cloud. They might start by deploying their API gateways on virtual machines with a goal of moving them to Kubernetes in 18 months. Many customers are on a journey with their infrastructure. It is critical that the same API gateway runtime can be deployed on these different platforms - it is no longer acceptable to have to deploy different gateway runtimes that support air-gapped networks or deployments in countries with strict data residency laws versus what you might be deploying onto your public cloud infrastructure!Īn estate of completely different API gateway runtimes means that your API program becomes fragmented with separate developer portals, inconsistent observability, completely different CI/CD pipelines, and you often have to accept the lowest common denominator when it comes to the delta in functionality between the different gateways. Every customer utilizes different infrastructure, whether that be bare metal, virtual machines, containers deployed on Kubernetes or serverless platforms. The first thing that I think about when I'm working with our customers to plan a deployment of an API management platform is where we are going to deploy it. Where your API gateways are deployed, how they are deployed and how they are configured might be obvious now, but it is likely that in 12 or 18 months, these will be very, very different!Ĭheck out the entire Kong vs Apigee Report for a complete overview of all features and capabilities Your Gateway Needs to Run Where Your APIs Do This is one of the key reasons why we built Kong - to fill the gaps left by first wave vendors like Apigee. In this blog post, I'll walk through why it's important that your API gateway provides the flexibility and agility to grow with your infrastructure and business as things change. This has resulted in the need to deploy your API gateway on the cloud AND fully on-premises AND anywhere in between to support all of the traditional, new and emerging API interaction patterns such as hybrid. ![]() ![]() The number of APIs has grown exponentially (over 100% year-over-year growth according to Gartner Research), and APIs are not just being exposed at the edge of the network but internally too. However, the world has changed considerably since then. They did this because it was the best option available at the time, and the first wave of API management vendors like Apigee had a solution that could support it. In the past, when the use cases were fairly simple, organizations would deploy an API gateway as a SaaS monolith in the cloud, sitting at the edge of the network. In the past couple of years alone, we've seen huge changes in the deployment patterns that our customers are adopting. The API management space is changing - fast.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |