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.
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.
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.
When setting up Kubernetes for the first time, one of the networking challenges you might face is how to safely grant outside clients access to your cluster. By default, pods within a cluster can communicate with all other pods and services. You should restrict access to anything outside of that group.
