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.

According to Deloitte, 96% of organizations are using APIs in 2021, representing a 16% increase from just last year. The value of APIs for modern-day organizations is hardly questioned, with Deloitte pointing out that they represent “a strategic enabler in modern enterprises to build up connected experiences and unlock value from existing data.” Is you business considering how API strategy fundamentals like technology integration can support your long term goals?

As your organization undergoes major digital transformations and starts adopting new technologies, it’s critical to evaluate how you’re currently looking at your technology assets. Do you see them as differentiated business capabilities? Adopting a product mindset with developing your API ecosystem becomes simpler when you can shift your focus away from the technical implementation process and its challenges and start focusing on your strategy and its relevant business outcomes.

SaaS applications generally tend to manage customer data in a multitenant database, meaning all customers share the same database. The data is secured, or segmented, by a unique identifier that maps a particular table record to a customer. This approach to data management means the SaaS can avoid the overhead and complexity of managing customer data within separate databases. Increasingly, SaaS customers are asking for API-based access to their data.