Kong’s Wanny Morellato and Deepak Mohandas recently joined Justin and Autumn on the ShipIt podcast to talk hybrid infrastructure with Kong Gateway and Kong Mesh. They unravel the complexities of hybrid infrastructure at scale, discussing the processes, strategies, and philosophies that drive continuous delivery, infrastructure as code, and more.

APIs have become fundamental to the digital economy, enabling integration and communication between different systems and services. A mature API platform is not just a technical achievement but a strategic asset that can drive innovation, efficiency, and growth. However, reaching this level of maturity requires a clear understanding of the stages involved and a commitment to evolving practices and strategies that best suit the organization's unique needs and goals.

The Kong Konnect team recently launched the Portal Management API, which allows users to manage their Developer Portals with one API. That means you can easily manage your portal settings, appearance, application registrations, and registration settings easier than before. In this blog, I’ll walk you through two scenarios that we expect the portal management API can help streamline.

Today we’re excited to announce that Kong Insomnia has shipped Storage Control, a new enterprise capability that allows administrators in an Insomnia organization to mandate what type of backend storage developers are allowed to use when creating API assets like API collections, API specifications, environments configuration, authentications data, and more.

Looking to develop more APIs faster (and securely)? Then you have some different API platform deployment models to consider. In this post, we'll define and compare the siloed, centralized, and federated API platform deployment models — and dive into why federated API management is key to striking a balance between agility and governance.

In this post, we're going to explore Karpenter, the ultimate solution for Node Autoscaling. Karpenter provides a cost-effective capability to implement your Kong Konnect Data Plane layer using the best EC2 Instances Types options available for your Kubernetes Nodes. See the previous posts in this series for more on Data Plane Elasticity and Pod Autoscaling with VPA, HPA, and Node Autoscaling with Cluster Autoscaler on Amazon EKS 1.29.

In the rapidly evolving landscape of API management, understanding the raw performance and reliability of your API gateway is not just an expectation — it's a necessity. At Kong, we're dedicated to ensuring our users have access to concrete, actionable data to guide their operational and development strategies.

In the rapidly evolving world of API management, the conversation around "the great unbundling of API management" has recently gained traction. This movement, highlighted by industry experts and analysts, including a recent Forbes article, reflects a shift towards a more componentized approach in API tooling offerings. Such an approach caters to the enterprise's specific needs, moving away from the traditional "does-it-all" solutions.

Today we’re launching the Kong Konnect Engineering Tech Blog, dedicated to exploring the technology challenges and solutions we’ve encountered. The objective? To offer valuable technical content that enables our readers to broaden their engineering expertise.

After getting our Konnect Data Planes vertically and horizontally scaled, with VPA and HPA, it's time to explore the Kubernete Node Autoscaler options. In this post, we start with the Cluster Autoscaler mechanism. (Part 4 in this series is dedicated to Karpenter.)