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.
The ability to rapidly assemble and reassemble APIs and microservices has become a competitive differentiator across all industries — allowing organizations to pivot business models and deliver amazing customer experiences at speed and scale. Innovative organizations are pushing to become agile and transforming by adopting cloud native technologies that allow them to build more resilient software quickly that easily scales.
At Kong, we’re always looking to expand the experience of running our products in the AWS cloud. As we steadily move into 2023, we want to continue this streak because we see firsthand the tremendous growth and success it provides our customers. Today, we’re excited to announce that the Kong API management platforms, Kong Enterprise and Kong Konnect, are validated integrations with Amazon VPC Lattice.
We’re happy to announce the release of Kong Ingress Controller (KIC) 2.9, in which we’ve taken significant steps towards solution extensibility, deployment flexibility, and lowering the cost of ownership. KIC now offers a number of features that we think you’ll be excited about: Here are the details about each of these features.
At the beginning of 2021, a brand new data team was assembled to build a real-time data platform for Kong’s SaaS platform, Konnect. Our mission is to provide top-notch real-time API analytics features for Konnect customers. V1 platform architecture The initial backend consisted of three main components: an ingestion service to handle incoming telemetry requests, an intermediate message queue, and a real-time OLAP data storage.
In this blog we are going to learn about the technical challenges behind solving GraphQL authorization and how many organizations resolve it today. Then discuss how a Kong / OPA integration can help drive security standards in this space and bring some parity with REST API solutions. Last, we will end with a quick tutorial.
