We’re happy to announce the general availability of Kong Enterprise 3.2. In this release, we’ve taken significant steps to ensure the smooth and reliable operation of our API management solution. In Kong Enterprise 3.2, we’ve delivered key functionality for customers that operate Kong Enterprise in a hybrid environment in order to further enhance its reliability. Specifically, we’ve expanded Kong Enterprise’s capabilities in the following areas.
Red Hat OpenShift is the industry’s leading enterprise Kubernetes platform that runs ubiquitously across on-prem, and the cloud. With Red Hat OpenShift Service on AWS (ROSA), a managed Red Hat OpenShift platform that runs natively on AWS, it is even easier to get kick-started on an enterprise-ready instance of Red Hat OpenShift in the cloud. Kong similarly distinguishes itself as a multi-platform, multi-cloud API Management solution pushing the vision of APIs.
Developers will remember times when they were trying to figure out why something they were working on wasn’t behaving as expected. Hours of frustration, too much (or perhaps never enough) caffeine consumed, and sotto voce curses uttered. And then — as if by fate — the issue is narrowed down to a simple oversight that makes perfect sense upon discovery. Problem solved!
In this post, we’ll talk about what APISecOps is, including the fundamentals of it and the personas involved. Then, we’ll discuss how API, microservice, and policy lifecycles integrate to produce a secure service in production, and why collaboration and API-Design First are essential for APISecOps success.
Looking to develop more APIs faster (and securely)? Then you have some different API platform deployment models to consider. In this post, we’ll define and compare the siloed, centralized, and federated API platform deployment models — and dive into why federated API management is key to striking a balance between agility and governance.
In this post, Nathaniel Reynolds, Associate Director of Informatics Architecture & DevOps at Moderna Therapeutics, talks about service mesh, removing limitations with open source, and how AI helps developers do more. No one can predict the future, but here’s a safe bet: in the next five to ten years, we aren’t going to have fewer applications. We’re going to have more. And that means connectivity requirements are going to get bigger and bigger over time.
Viktor Gamov also contributed to this post. In recent decades it’s become common for communication between backend services to employ HTTP APIs with JSON payloads. Many HTTP APIs adhere (or at least aspire) to REST Principles, though many fall into a category we’ll call "REST-like".
Since our last Kong Konnect monthly update, we’ve been hard at work to deliver some more powerful features in Kong Konnect, including consumer groups, dynamic client registration using Curity and Auth0, plugin ordering, and streamlined Docker runtime instance creation. Read on to learn what’s new in Kong Konnect.
We’re excited to announce the release of Kong Mesh and Kuma 2.1! In this release, we’re shipping the full suite of new and improved policies announced (and started) in 2.0. Additionally, we’re launching some more great UX improvements in the UI and a host of smaller fixes. In order to take advantage of the latest and greatest in service mesh, we strongly suggest upgrading to Kong Mesh 2.1. Upgrading is simple through kumactl or Helm.
