Kong Gateway 3.0 is an important milestone that introduces the next evolution of our cloud-native API platform. Both the enterprise and open source editions of Kong Gateway 3.0 are available now from your favorite distribution channels. With Kong Gateway 3.0, we are introducing many powerful features that deliver the following key benefits:
Christian Heidenreich and Sunny Xia also contributed to this post. We’re excited to announce a new release of Kong Konnect, the end-to-end SaaS API lifecycle management platform. This release introduces a number of brand new features as well as improve existing features that empower you to efficiently publish, consume, secure, analyze, and manage APIs and services across all your applications in any environment. Read on to learn more about the new capabilities in Kong Konnect.
There are many pros and cons for both GraphQL and REST APIs, but one of the areas where GraphQL really shines is API composition. Taking data from multiple APIs and combining them to make something new is a key part of delivering a useful service.
Security best practices remain a top priority for enterprises, especially as high-profile hacks and cybersecurity breaches pose increased risks. According to the 2022 Morgan Stanley CIO survey, IT spending is expected to reach 4.4%, with cloud computing and security software as the leading verticals. This rapid digital transformation across sectors presents organizations with opportunities, along with some new challenges.
Our latest release of Kong Konnect augments the security and compliance of the offering through enhanced authentication capabilities. Through the rest of this post, we’ll walk you through each of these features and explore what’s new in this Kong Konnect release.
Kong Gateway is built on Nginx/OpenResty because it has a unique master/worker architecture, forks out many worker processes, and can utilize every CPU core efficiently. It is the powerhouse within Kong. But one master / multi workers architecture has an annoying defect. Each worker is an isolated process, so it is hard to share something with each other, and in Kong Gateway, there’s a lot of information to communicate between workers, like rebuilding router/health check/cluster sync, etc.
