In part 1 of this series, we started a journey from the planet-spanning infrastructure layer to what happens inside a single Kong worker, similar to an office building in complexity. In this second part, we’ll dive a bit deeper—we’ll see who the occupants of that office building are and the kind of life they live.
Today, we’re thrilled to announce the general availability of Kong Ingress Controller 2.0 (KIC) – the most robust, scalable, and extensible version of our Kubernetes Ingress Controller to date. This is a major milestone both for the KIC product as well as for the Kong community as a whole. In addition to KIC 2.0’s new features, it also sets the foundation for us to more rapidly improve the user experience and add more capabilities.
Today, Application Programming Interfaces (APIs) and microservices are the de-facto standard for building and connecting modern applications. APIs are no longer just a delivery mechanism but have become the product itself. API lifecycle management refers to the comprehensive, step-by-step process of planning, developing, implementing, testing, and versioning an API.
These days, a lot of companies are moving towards cloud native applications and declarative configurations. This is also true for the traditional API gateways (e.g., MuleSoft, Axway, etc). Customers are looking for new technologies which fit better in their cloud environments and also are faster and cheaper. The main challenge here is how to migrate the existing APIs to the new platform.
In this episode of Kongcast, I had the pleasure of speaking with Viktor Farcic, developer advocate at Upbound, about why empowering developers to manage the full application lifecycle helps app development teams increase efficiency.
In this three-part blog series, we examine the critical role Kubernetes plays in shaping the future of infrastructure, including the rise of containers and Kubernetes. The first in the series covers Next-Generation Application Development. The second covers the Next Frontier: Container Orchestration. And the third covers How Kubernetes Gets Work Done.
