Today, we have some exciting news! We’re announcing our $43 million Series C round, led by Index Ventures and our board member Mike Volpi, with participation from existing investors Andreessen Horowitz (Martin Casado) and Charles Rivers Ventures (Devdutt Yellurkar), as well as new strategic investors GGV Capital and World Innovation Lab (WiL).
Today, we’re thrilled to announce the release of Kong 1.1! Building on the release of support for service mesh in Kong 1.0 last September, our engineering teams and community have been hard at work on this latest iteration of our open source offering. With new Declarative Config and DB-less deployment capabilities, as well as numerous small improvements and fixes, Kong 1.1 is one of our most exciting releases to date!
This post is the last in a three-part series about deploying Kong as a service mesh. The first post discussed how we define the term “service mesh” here at Kong, and the second post explained the architectural pattern used to deploy Kong as a mesh. In this post, we will talk about the new features and configuration options we added to give Kong its mesh capabilities.
In the modern SaaS world, observability is key to running software reliability, managing risks and deriving business value out of the code that you’re shipping. To measure how your service is performing, you record Service Level Indicators (SLIs) or metrics, and alert whenever performance, correctness or availability is affected.
API Fortress is a continuous testing platform for APIs. We’ve been a friend to Kong since the beginning. In this guest blog post, we explain how our company uses Kong to facilitate the process of virtualizing APIs.
Four months ago, we declared that API Management is dead and announced our vision for a service control platform. Today, we’re taking a critical step towards fulfilling that vision with the launch of artificial intelligence and machine learning additions to the Kong Enterprise platform – Kong Brain and Kong Immunity.
