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.
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.