Systems | Development | Analytics | API | Testing



Kong Named Leader in Gartner Magic Quadrant for Full Life Cycle API Management for Third Year

For the third consecutive year, we’re happy to announce that Kong has been recognized as a Leader in the Gartner Magic Quadrant for Full Life Cycle API Management and is positioned furthest to the right for Completeness of Vision. This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document.

Introducing Kong Gateway Operator

In our next #KongBuilders #livestream on November 16, Viktor Gamov from Kong will deep dive into Kong Gateway Operator. Kong Gateway Operator is a next-generation deployment mechanism founded on the operator pattern that allows Kong Gateways to be provisioned in a dynamic and Kubernetes-native way, enabling automation of Kong cluster operations and management of the Gateway lifecycle.

[Tech Talk] Advanced Service Mesh - Build and Manage Multi-Cloud Applications Using Kuma

A service mesh helps to make service communication more secure, reliable and traceable in distributed system architectures. In connection with the topic of service mesh, we often think of terms such as microservices, containers or Kubernetes; i.e. terms from the orbit of modern design methods, architectural approaches or technologies. Of course, everything is usually cloud-based.

How to Use Prometheus to Monitor Kong Gateway

Observability is a critical part of Kong’s API Gateway. In this post, we’ll describe two options to monitor Kong Gateway using Prometheus. Prometheus is an open source system monitor toolkit built at SoundCloud that is now widely adopted. StatsD was originally a simple daemon developed by Etsy to aggregate and summarize application metrics. Prometheus provides a StatsD exporter to collect metrics that are sent in StatsD format.

What's new in Kong Gateway 3.0 with Michael Heap and Guanlan Dai | #KongSummit22

What’s next for Kong Gateway? Join us as we reveal the next evolution of Kong's cloud-native API platform. Businesses are fighting to build exceptional digital experiences to stay ahead — and that means an explosion of demand for APIs. But with more APIs to design, run, and govern, you have to juggle managing APIs across mixed and complex environments, scaling to the demand of web applications, and ensuring compliance and security as APIs become the number one attack vector.

Beyond the API Gateway - Kong's Product Vision & Strategy: VP, Product, Reza Shafii, Kong Summit 22

Beyond the API Gateway- Kong's Product Vision and Strategy API Management as it was once known is dead. Kong's Vice President of Product Reza Shafii talks through the evolutions of monoliths to microservices and beyond, the birth of Kong, as well as the growth and future of Kong in his Kong Summit 2022 keynote. Learn about the Kong suite of products, how businesses can better supporting their dev ops functions, catch a recap of a live demo of Kong Insomnia and more.

Kong Mesh and Kuma 2.0 Released with eBPF Support, Next-Gen Policies, UI Improvements

Today we’re excited to announce the release of Kong Mesh and Kuma 2.0. With this new major release, we’re announcing the first availability of our next-generation policies, in addition to new eBPF capabilities. 2.0 is also significant as we have unified the version scheme between Kong Mesh and Kuma. Previously, Kuma versions had an n-1 version naming convention when compared with Kong Mesh.


Transforming Kong Logs for Ingestion into Your Observability Stack

As a Solutions Engineer here at Kong, one question that frequently comes across my desk is “how can I transform a Kong logging plugin message into a format that my insert-observability-stack-here understands, i.e. ELK, Loki, Splunk, etc.?” In this blog, I’m going to show you how to easily accomplish converting a Kong logging payload to the Elastic Common Schema. In order to accomplish this task, we’re going to be running Kong Gateway in Kubernetes and using two Kong plugins.


Dynamic Routing Based on JWT Token's Claim with Kong Konnect

A common use case that is frequently requested is how to dynamically route requests based on authentication attributes. An example of this technique is routing requests to relevant upstream services based on claims contained in a JWT token. Admins would like all their clients to go to the same URI as it makes the implementation easier. But behind the scenes they might need to tailor specific configuration/applications for them, hence routing their request based on their identity.