Today, we are proud to announce the general availability (GA) of Kong Gateway 2.5! Below, we’ll dive deeper into some of the new features and capabilities this release brings. Be sure to upgrade or try out a fresh install today! 2.5 compatible releases will be available with Konnect, our SaaS platform, shortly!
APIs come in all different shapes and forms. In this tutorial, I’ll show you a Kubernetes Ingress gRPC example. I’ll explain how to deploy a gRPC service to Kubernetes and provide external access to the service using Kong’s Kubernetes Ingress Controller. And to hype you up a little bit about the upcoming live-action movie, Dune, based on Frank Herbert’s book, I created a Kubernetes service that delivers Dune quotes.
Last week, the digital world experienced a power outage. A major distributed edge computing platform experienced a software bug that led to the collapse of their Domain Name System (DNS), or the Internet’s way to map domain names (i.e. united.com) to IP addresses. The consequences were costly. So what is the real cost of downtime? When a DNS system within a globally recognized edge platform fails, it causes downtime for a huge amount of international enterprises.
API gateway request transformation policies are incredibly powerful. There are many situations when an API developer can take advantage of request transformations to adjust the shape and values of a request to cleanly fit their API. Let’s say you’re deprecating a certain endpoint for your API, but you still need to support the old specification for a transition period.
A true service mesh should focus on how to manage and orchestrate connectivity globally. Connecting a new service mesh for each use case is a much simpler problem to solve, but doing so won’t help you scale. You’ll just be throwing a service mesh in each cluster and calling it a day. The more appealing solution is to stitch together environments.
This blog post is part two of a two-part series on how we broke down our monolith to scale our API management with Kong Gateway, the world’s most popular open-source API gateway. (Here’s part one.) At NexJ, the pioneer of intelligent customer management with client engagement products designed for the financial services industry, we sought to capture the full addressable market by breaking down the monolith and going API-first.
