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.

We are happy to announce the release of Kong Mesh 1.9 and Kuma 1.8! This release is packed with features and improvements such as observability for builtin Gateway, a complete rewrite of the CNI and projected service account tokens support. In order to take advantage of the latest and greatest in service mesh, we strongly suggest upgrading to Kong Mesh 1.9.

The pace of the industry today is pressuring software developers to build, test, and release software more frequently than ever. To achieve this pace, teams have built two core processes into their workflow: Continuous Integration and Continuous Deployment. Continuous Integration and Continuous Deployment (CI/CD) is a subset of the DevOps workflow that automates application code management and its safe, predictable shipping. In this article, we’ll take a deep dive into CI/CD.

As more companies are undergoing digital transformation (resulting in a huge explosion of APIs and microservices), it’s of paramount importance to get all the necessary data points and feedback to provide the best experience for both users and developers. Kong Gateway is a lightweight API gateway that is built to be open and versatile. Regardless of the technology stack involved, Kong supports these monitoring or logging requirements through its extensive ecosystem of plugins.

As engineers and architects, we automatically build resilience into platforms as far as possible. But what about the unknown failures? What about the unknown behavior of your platform? The philosopher, Socrates, once said “You don’t know what you don’t know”. What if I could tell you there is a way to turn these unknowns into knowns – a way to understand how your platform will behave to specific failure events…

We live in a digital economy where Application Programming Interfaces (APIs) are foundational elements for businesses to operate and grow. As rightly outlined by Gartner, APIs interconnect individual systems that contain data about people, businesses and things, enable transactions, and create new products/services and business models. The popularity of APIs has grown significantly in the last decade or so, but the history of APIs stretches back much further.

In our last blog post, we traced the evolution of APIs in the cloud age. The cloud age introduced the idea of an “API economy” — or the business practice of organizations exposing their digital services or information through the controlled use of APIs. While the API economy looks attractive today, we believe it will become even stronger in the future.