We’re in the middle of the golden age of innovation that’s creating absolutely astounding achievements. Within 10 years, Elon will land people on Mars, Germany won’t have any gasoline cars on the road, and you’ll be able to use more of your senses in virtual reality. This blade cuts both ways though.

Hey there, Kong Nation! We are happy to announce the release of the community edition of Kong Gateway 2.3, our flagship open source API gateway! Version 2.3 brings several exciting new features as well as some significant security improvements. As we have done in both versions 2.1 and 2.2, we are also releasing a Beta version of the Enterprise 2.3 gateway while incorporating all features from the open source 2.3 gateway.

We created the Terraform API gateway module to help you follow DevOps best practices while implementing Kong using infrastructure as code (IaC). Terraform is an open source tool that allows you to implement IaC using a declarative declaration definition. This Terraform module is the reference platform maintained by Kong for potential and existing customers to quickly set up both Kong Gateway and Kong Enterprise for demo and PoC environments.

Rate limiting protects your APIs from inadvertent or malicious overuse by limiting how often each user can call the API. Without rate limiting, each user may make a request as often as they like, leading to “spikes” of requests that starve other consumers. Once enabled, rate limiting can only perform a fixed number of requests per second. A rate limiting algorithm helps automate the process. In the example chart, you can see how rate limiting blocks requests over time.

As a developer, your company hired you to build incredible products that focus on your users’ and customers’ needs. Yet, in the age of microservices, producing the best products relies heavily on efficient cloud service connectivity. For example, an eCommerce marketplace is more than a front-end UI that customers access via a browser.

Transitioning to microservices has many advantages for teams building large applications that must accelerate the pace of innovation, deployments and time to market. It also provides them the opportunity to secure their applications and services better than they did with monolithic codebases.

This article was written by Ivan Rylach, a staff software engineer from Checkr. Checkr is the leading technology company in the background check industry. The company was moving to a services-oriented architecture. To scale this process, we switched to a declarative configuration for API management. As the staff software engineer at Checkr, I faced more scenarios where declarative configuration was not suitable by design. This post, and the video below, will explain these cases.

In 2020, the acceleration of digital transformation quickly emerged as a top priority for many organizations as they grappled with the business impacts of an unexpected pandemic and raced to adapt to a new reality. As businesses begin to pivot out of the shadows of COVID-19 in 2021, what will this new reality look like? What new technology trends will emerge? Our executives shared their personal predictions for the year ahead: 1. The End User Era: Architects Will Rise in IT Purchase Power

Building a multi-region or multi-cloud environment for your applications requires a lot of attention. In a typical deployment, you would have an API gateway running close to the several application runtimes. You should enhance your deployment to support different regions in a given cloud, or in an even more distributed and hybrid scenario, multiple services running across other public clouds and on-premise environments.

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.