Kong is proud to announce the release of the latest version of Kong Mesh 2.3. In this release, Kong Mesh continues to build upon the enterprise-grade service mesh in the critical areas of, security, flexibility, and resiliency. As organizations continue to leverage APIs to deliver digital experiences they rely more heavily on the underlying infrastructure that a mesh provides.
By now, when we hear the words “service mesh” we typically know what to expect: service discovery, load balancing, traffic management and routing, security, observability, and resilience. So, why Kong Mesh? What does Kong Mesh offer that would be more difficult to obtain with other solutions? Why is Kong Mesh with Red Hat OpenShift a great pairing? We’re happy to announce that the Kong Mesh 2.2.0 UBI Images are available in the Red Hat Ecosystem Catalog.
API monetization is currently a trending topic for many organizations looking to beef up their revenue. Of course, monetizing APIs isn’t the easiest of tasks and requires quite a few moving parts. When it comes to monetization, you’re going to need an entire technology stack to handle the heavy lifting. Creating a stack that allows you to build a product and get to market rapidly is great.
Enterprises are investing in data mesh initiatives to accelerate how decisions are made and to create novel experiences based on machine learning models. Similarly, enterprises are investing in API platform initiatives to productize business domains (or bounded contexts in domain-driven design parlance) as self-service digital assets that accelerate innovation and improve business agility. Both initiatives are typically run as separate work streams.
We’ve just shipped Kong Ingress Controller (KIC) 2.10! This release makes KIC easier to use. In this blog we’ll cover: You can read the CHANGELOG for full details, but for now, let’s focus on the highlights.
