Systems | Development | Analytics | API | Testing

The latest version of Kong Mesh brings an improved provisioning experience and streamlined management of policies — plus user interface enhancements to elevate your experience deploying and managing Kong Mesh. Built on top of Kuma, Kong Mesh is a service mesh designed to provide security, observability, and traffic control across modern, distributed applications.

We’re excited to announce the general availability of Kong Insomnia 11! This release introduces third-party vault integrations for enhanced security, an all-new Git sync experience for more seamless collaboration, and support for multi-tabs to improve efficiency within the Insomnia application. Keep reading to learn more.

When your company deployed its first large language model last quarter, your CTO probably didn't mention you'd need entirely new tools to understand what's happening under the hood. But here we are. AI Observability isn't just another tech buzzword—it's the difference between confidently leveraging AI and crossing your fingers hoping nothing breaks.

We're thrilled to announce the tech preview of Active Tracing, a significant advancement in Kong Konnect. This innovative feature unlocks unparalleled visibility into API traffic as it flows through Kong Gateway, empowering you to optimize performance, troubleshoot issues, and refine your API strategies.

APIs are the fuel of modern innovation, but they have to be discoverable and easily consumable to drive the maximum possible value. Without an easy-to-use, developer-friendly discovery layer, Developers are stuck searching across disparate repositories for APIs, or — even worse — wasting time and effort building redundant APIs. The market has already responded to this need with the API Developer Portal concept, where the portal acts as a central catalog for all APIs.

Earlier this year the Kong Konnect Analytics team was looking to leverage the stability and flexibility of our own Kong Gateway to handle the entire load of our Analytics ingest firehose. Almost all Konnect API traffic flows through a Kong Gateway and most of it has from the very beginning. For some legacy and differing protocol reasons, our Analytics ingest service was not included in our initial Kong Gateway configuration.

Choosing the right API architecture is crucial for building efficient and scalable applications and the two prominent contenders in this arena are GraphQL and REST, each with its unique set of characteristics and benefits. Understanding the similarities and differences between these two approaches can help teams make informed decisions when designing APIs. This article aims to provide a comprehensive comparison of GraphQL and REST, highlighting their key features, advantages, and use cases.

As the need for speed in business can seemingly be at odds with the need for control, organizations developing APIs today face a critical challenge: how can you empower developers to build and deploy APIs quickly while maintaining enterprise-wide governance and security? More traditional API deployment approaches are often to blame for why API initiatives fail to deliver the promised benefits as complexity and scale increase.

When speaking with platform teams who are responsible for setting up their organizations’ API platforms, we often hear: "We really want to offload the infra side of this. We don’t want our engineers spinning up their own locally hosted infrastructure or asking other infrastructure teams to do this.

This blog addresses the common challenges organizations face with fragmented API management in Kubernetes environments and presents Kong Konnect combined with the Kong Ingress Controller (KIC) as a comprehensive solution.