Systems | Development | Analytics | API | Testing

Today we’re pleased to announce a new strategic partnership and resale agreement with Imperva. Imperva customers will now be able to directly license Kong Enterprise, the fastest, most feature-rich, and secure API management solution. In addition, Kong customers will be able to use the Imperva API Security plugin within Kong Enterprise. This allows developers to comprehensively secure their APIs and protect their business applications and data against unauthorized access.

At Kong, our mission is to deliver the best API lifecycle management experience for the cloud native era. Driven by our dedication to meeting the dynamic demands of modern end-to-end API management, we’ve introduced an array of new Kong Konnect features in April, enhancing functionality and elevating the user experience.

As we continue to push the boundaries of API management, we’re excited to announce the beta release of Kong Ingress Controller within Kong Konnect. Revealed at KubeCon + CloudNativeCon Europe 2023, this new integration turns Kong Konnect into the world’s first modern unified end-to-end API management platform.

We’re excited to announce the release of Kong Mesh and Kuma 2.2. This new minor release adds some long-awaited enterprise features, more incremental improvements to our UI and policies, and many more minor features and bug fixes. In order to take advantage of the latest and greatest in service mesh, we strongly suggest upgrading to Kong Mesh 2.2. Upgrading is easy through kumactl or Helm.

At first glance, that does not make sense, right? The title suggests you should invest your DevOps/Platform team’s time in introducing a new product that most likely will: Through this article, we’ll show you that even though those initial concerns are justified, the overall benefits that can be realized by adopting a service mesh can outweigh any initial effort and investments.

As the world’s most popular API Gateway, Kong Gateway is flexible and can be adapted to various environments and deployment configurations. This flexibility means some time should be taken to make good architectural decisions for the use cases in mind. For example, the best configuration for a developer’s workstation isn’t the ideal one for a high SLA deployment. Fitness for purpose is therefore the objective.