Starting with the 3.3 release, Kong Gateway includes a new implementation of the internal queues that are used by several plugins to decouple the production of data in the proxy path and its submission to a receiving server, such as a log server. We’ll walk you through why queues are needed, why a new implementation was required, how the new implementation works and how queues are configured.
As API usage and dependence continue to grow, the need for a reliable, performant, and secure API gateway has become even more essential. Kong Gateway Open Source continues to be the world’s most adopted API gateway, setting the benchmark for performance, reliability, and observability. Today, we’re excited to unveil Kong Gateway 3.3 for Open Source, a release that once again elevates the API gateway experience to new heights.
There are many different ways to deploy Kong Gateway. In this post, Viktor Gamov (Principal Developer Advocate at Kong) walks through the four most popular ways. Depending on your particular use case, you may find that one or more of these is a good fit. Let’s get started!
We’re excited to announce the general availability of Kong Enterprise 3.3. In this release, we’ve taken significant steps to deliver an enhanced experience for developers by making Kong Enterprise even more enterprise-ready and robust. Additionally, we’ve checked a few important boxes for our customers to easily comply with regulations. In this blog we’re going to cover the following key features we are delivering as part of Kong Enterprise 3.3.
In this Kongcast episode, Danielle Dias, Software Engineer at Just Eat Takeaway.com, talks about how her team creates a seamless customer experience by using Kong Gateway for rate limiting, monitoring, alerting, and more. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.
Event streaming allows companies to build more scalable and loosely coupled real-time applications supporting massive concurrency demands and simplifying the construction of services. Ultimately, we may need to grant access to such infrastructure to the most diverse entities, including external applications posting events that will be eventually consumed by internal systems. The purpose of such exposure is to promote development teams’ collaboration.
We’re thrilled to announce the latest release of Kong Insomnia, version 2023.2.0, packed with improvements and fixes that will make it even easier to manage your APIs. In this release, we introduce an enhanced Import flow, along with support for Kong 3.0 and the return of Swagger/OpenAPI preview. Continue reading to learn more about these exciting updates.
Today we’re honored to announce Kong has been recognized as a 2023 Customers’ Choice in the Gartner® Peer Insights™ for Full Life Cycle API Management. We believe this endorsement highlights the trust and passion Kong’s customers have for Kong’s cloud native API platform to deliver speed and scalability, unleash developer productivity, and ensure security and governance But hey — don’t take our word for it.
Creating API design guidelines is a common practice for many enterprises. The goal? Ensuring that all teams involved in API development will adhere to them. However, this goal is often not achieved, as developers may not take the time to read, study, and apply these guidelines. To address this issue, API design guidelines should be seen as the foundation to create high-level tools and services that enable developers to focus more on business logic and less on API integration boilerplate.
APIs have become the backbone of modern software development, by facilitating seamless communication between applications and systems. But building an effective API requires more than just good coding skills. It also requires careful monitoring and analysis to ensure optimal performance, security, and adoption. Additionally, creating accurate and in-depth reports can be time-consuming and complicated, especially when dealing with large data sets.
