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.
As we take stock of how COVID-19 has affected the way we operate, nothing in technology is more apparent than the switch to digital. Although many of us have transitioned from water-cooler conversationalists to reluctant zoom dwellers, the impact on business processes themselves might actually be more profound. According to McKinsey, coronavirus has acted as an accelerant on companies offering digital products and services.
In this article, we’re going to build a fun and simple gRPC server in Node.js. Then we’ll demonstrate how to use Insomnia to make gRPC requests on our server. First, let’s briefly cover some core tech concepts. If you’re already familiar with the basics, skip ahead to the tutorial or watch the video below.
This blog post is part one of a two-part series on how our team at NexJ broke down our monolith to scale our API management with Kong Gateway, the world’s most popular open source API gateway.
How do you choose an API style and API technology when you start a new project? Today, if you look at API technology research such as RapidAPI Developer Survey and Insights, you’ll probably conclude that REST is the dominant force in the API landscape. While REST is certainly well-known to most developers and used in a lot of production environments, it may not be the best fit for every scenario.
Hello, Kong Nation 👋 ! We’ve fashioned a pristine version of the Kong Gateway (OSS) 2.5, which is now available on the normal channels. Read on for more release information.
Over the past ten years, Clubhouse and other innovative startups built software quickly. They started from scratch and blew past their incumbents. But the fact of the matter is that speed is no longer a differentiator. Everyone can move quickly. We’ve seen it as Facebook and Twitter quickly duplicated Clubhouse’s “innovative” functionality. Today, it’s all about agility—taking the momentum that you’ve already built up.
APIs have long been the programmers tool of choice for inter-application communication. Built by programmers, for programmers. Giving each other an interface and a means by which to call each other’s code. As for documentation and ease of use, well….
Think back to when your development team made the switch to Dockerized containers. What was once an application requiring multiple services on virtual machines transitioned to an application consisting of multiple, tidy Docker containers. While the result was a streamlined system, the transition likely was daunting. Now, it’s time for another transformational leap: moving from a single set of containers to a highly available, orchestrated deployment of replica sets using Kubernetes.
Hello, everyone! Viktor Gamov, a developer advocate with Kong here. In this article, I would like to show you how to set up service connectivity using Kong Konnect and Kubernetes. I will deploy an application in Kubernetes, configure a runtime through Konnect and demonstrate some management capabilities like enabling plugins. Let’s dive right in!
MS3 specializes in enterprise integration software, cloud migration strategies and API enablement. I’ve worked at MS3 for about five years. For the last year, I’ve been the principal product manager for Tavros, an enterprise integration platform from MS3. This article will dive into how we’re leveraging Kong Gateway and Kuma service mesh in Tavros.
Co-authored by Samta Bansal More than two million British people use Open Banking-based products today, a number that, despite the disruption of COVID-19, is double that seen at the start of 2020. No wonder International Banker dubbed 2021 “The Year of Open Banking.” As open banking spreads worldwide, its growth comes with the pressing need to drive standardization that bridges geographic boundaries and regulatory frameworks.
