Navigating the transition from monolith to microservices can be an ambitious undertaking for any organization. Today, we’re launching our new Kong GTM Partner Program to create a global ecosystem of experts to help organizations successfully transition to microservices, service mesh and other modern architectures.
The cloud native paradigm for application development has come to consist of microservices architecture, containerized services, orchestration, and distributed management. Many companies are already on this journey, with varying degrees of success. To be successful in developing cloud native applications, it’s important to craft and implement the right strategy. Let’s examine a number of important elements that must be part of a viable cloud native development strategy.
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.
With Kong 1.0 users are now able to control TCP (Transport Control Protocol) traffic. Learn about how we added TCP support, and how you can try it out. TCP traffic powers email, file transfer, ssh, and many other common types of traffic that can’t be handled by a layer 7 proxy. Our expansion to layer 4 will enable you to connect even more of your services using Kong.
