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. (Here is part 2.)
In a recent presentation at Destination: Scale, I gave an inside look into how NexJ, the pioneer of intelligent customer management with client engagement products designed for the financial services industry, expanded our customer base utilizing modern architecture focused on scalability and connectivity.
We set out to pivot our target audience beyond mostly large clients with on-premise environments to include smaller firms with diverse, cloud-centric deployments. As NexJ provides products within wealth management, private banking, commercial banking, corporate banking, sales, trading & research, and insurance, we offer specifically tailored solutions for the unique requirements of each sub vertical.
Our customers typically have a massive number of users and many systems integrated into each deployment. These deployments have been mostly on-premises with large clients such as Wells Fargo, UBS and Royal Bank of Canada, sometimes with 12,000-35,000 users and 12-19 integrated systems. Previously, we serviced these clients with a monolithic architecture on classic virtual machines, but challenges arose when we looked to scale and service smaller clients who often avoided on-premises installation due to cost.
To address the growing market and win smaller deals with a subscription model, we required a more flexible architecture that would not compromise current deployments. The ideal solution would need to be able to be deployed in one place, serve multiple clients, and reduce operational and maintenance costs without interrupting workflow during the transition.
Naturally, the team examined cloud providers and their services, but ultimately opted for an API-first model to define APIs and integrations and build applications. With the meteoric rise of cloud applications, connectivity was the core requirement – to interlace our applications and data as well as third-party integrations, particularly with financial services ecosystems, with seamless transitions. An API management platform was the key to tie this connectivity fabric together and improve process and collaboration throughout the company.
Embracing an API-first model would allow us to add new services and technologies swiftly without having to architect the entire system. The challenge, however, was to decouple the large monolithic application to deploy in the cloud and integrate with standard cloud applications using OAuth2 authentication, while also securely exposing APIs for third-party integrations. With this, the team went on the hunt to compare API management platforms, including Kong.
We ultimately selected Kong to expose our APIs and use Kong Gateway for a unified and consistent interface across applications. Kong enabled us to design our APIs, formulate standards and maintain a uniform appearance for the client despite changes on the backend such as technology stack adjustments or API version or structural changes.
Kong's Dev Portal was also critical in providing a seamless experience for our developers to track workspaces, services and routes as well as integrations for application monitoring and API tracing. Most importantly, Kong provided robust zero-trust security to meet global financial industry standards.
Today, we aim to expand our use of Kong to monitor API usage, subscriptions, and tracing, implement a GitOps integration and evaluate Kong's recently announced generally available service connectivity platform, Kong Konnect.
To watch the full presentation recording, click here. In part two of this blog series, I will take you through how we implemented Kong at NexJ.
While many organizations mistakenly believe a single tool can solve all their API security woes, the truth is far more complex. This blog post will dismantle the myth of the "silver bullet" and demonstrate how a comprehensive, defense-in-depth strat
Ever feel like you're fighting an uphill battle with your API strategy? You're building APIs faster than ever, but somehow everything feels harder. Wasn’t API-first supposed to make all this easier? Well, you're not alone. And now industry analys
This year, at our in-person API Summit , we’re excited to shine a light on the projects and people who aren’t just implementing Kong, but reinventing it. The Kong Innovator Awards recognize outstanding and future-facing projects from Kong custome
Survey Says: Google LLMs See Usage Surge, Most OK with DeepSeek in the Workplace Enterprise adoption of large language models (LLMs) is surging. According to Gartner , more than 80% of enterprises will have deployed generative AI (GenAI) applicatio
Kafka delivers massive value for real-time businesses — but that value comes at a cost. As usage grows, so does complexity: more clusters, more topics, more partitions, more ACLs, more custom tooling. But it doesn’t have to be that way. If your tea
A Practical Look at When (and When Not) to Use Ambient Mesh The word on the street is that ambient mesh is the obvious evolution of service mesh technology — leaner, simpler, and less resource-intensive. But while ambient mesh is an exciting develop
I'm commonly asked by customers for advice on how they can build a good platform cross-charging model for their organization. And my gut reaction is nearly always "don't." We'll come back to why I think that later, but first let's look at what cross