In Kong, plugins can be thought of as policy enforcers. In the case of rate limiting, Kong offers two plugins: An open source one and Enterprise. Both plugins can limit requests per consumer, route, service or globally. Configuring the same plugin is also possible on a more than level. When this occurs, an order of precedence is used to determine which configuration to run. With this capability, it is possible to apply fine-grained policy control. In this article, we cover an advanced use case.

When testing APIs, software engineers often repeat identical values across multiple requests, but who wants to waste time typing the same values every time? Insomnia’s environment variables solve this problem by allowing you to define a value once as an environment variable and reference that value wherever it’s needed. Insomnia also enables you to override certain variables using sub-environments or folder environments.

We’re happy to announce the release of gRPC support for Insomnia, now available in the 2020.5 release. With gRPC support, developers can make requests to gRPC backend services just like they can today with REST / GraphQL services from Insomnia.

You’ve decided to install Kong Gateway. Congrats! You’re almost ready to accelerate your microservices journey with the world’s most popular open source API gateway. This article and video will guide you through the short version of our tutorial. If you prefer, here are some more detailed instructions. If you haven’t already, make sure you’ve installed Kong before getting started. It should only take a few minutes.

After having announced Kuma 1.0 GA with over 70+ new features and improvements (and Kuma 1.0.1 this week), we are finally happy to announce a new major version of Kong Mesh that includes all the latest Kuma features – and more – in a fully supported enterprise package. With Kong Mesh 1.1 we can now deploy the most advanced enterprise service mesh in production across every cloud and private datacenter, on both Kubernetes and virtual machines.

We are happy to announce the release of Kuma 1.0.1 with a few improvements and fixes, and we suggest to upgrade to start using the greatest and latest. This is a minor update on top of Kuma 1.0 that shipped last week with over 70+ features and improvements. For a complete list of features and updates, take a look at the full changelog. Join us on our community channels to learn more about Kuma, including our official Slack chat.

From the Kong API Gateway perspective, using Consul as its Service Discovery infrastructure is one of the most well-known and common integration use cases. With this powerful combination more flexible and advanced routing policies can be implemented to address Canary Releases, A/B testings, Blue-Green deployments, etc. totally abstracted from the Gateway standpoint without having to deal with lookup procedures.

We are in the midst of an explosion of APIs and microservices. For some, the first instinct of creating an API is to get down to building one. Some level of planning will help manage the quality of APIs when working within a team. In this series of blogs, we will be sharing some guidelines on service design while working on API projects with Kong. Let us start by focusing on how to go about designing APIs that end up as entities that the Kong API Gateway runtime understands.

Today is a big day for Kuma! Kuma 1.0 is now generally available with over 70 features and improvements ready to use and deploy in production to create modern distributed service meshes for every application running on multiple clusters, clouds, including Kubernetes and VM-based workloads. Before we unpack this release, a big thank you to the community and to the users that have helped releasing this major version of Kuma with their contributions and feedback.

Today, we’re proud to announce the release of Kong Enterprise 2.2 GA! Kong Enterprise 2.2 is built on top of version 2.2 of our popular open source gateway and brings with it a slew of new features and some Enterprise-only features on top. Let’s dive in! For a long time, Kong has supported not only HTTP/HTTPS traffic with REST and gRPC APIs, but also raw TCP streams. In version 2.2, we now extend our support to include UDP-based protocols as well!