Back to Client Stories
Client Success Story

JLA: Unifying Operationswith Hybrid Cloud Integration

TL;DR: JLA, an investor venture-backed powerhouse with aggressive targets for operational profitability and growth. Through organic scaling and acquisitions, they grew exponentially, but their technology stack hit a wall.

We reached out to Razor with an almost impossible predicament – complex multi-system integration, in a tight timescale on a new strategic, cloud-based integration platform.

The Razor team were easy to engage with, understood the problem swiftly, were very competitively priced and most importantly their experts went above and beyond to successfully deliver a working and right solution for us.

Matt Sharp
Matt Sharp
Group Technology Officer at JLA

Ready to build your next game-changing platform?

Discover how bespoke engineering can transform your complex challenges.

The Challenge

JLA, an investor venture-backed powerhouse with aggressive targets for operational profitability and growth. Through organic scaling and acquisitions, they grew exponentially, but their technology stack hit a wall.

The challenge was distinct: Three critical systems, including a non-live financial platform, were sitting in silos. They were hosted on-premise, heavily customised, and stubbornly disconnected. JLA needed significant investment in automation to meet their deadlines, but they also needed to bridge the gap to Microsoft’s Azure cloud platform without breaking the business.

The "Wrapper" Strategy

We didn't just dive in; we started with deep discovery and technical spikes to challenge every assumption. The beast in the room was IFS, the primary financial system.

 

The IFS implementation was unique to JLA, loaded with complex, bespoke customisations that made standard integration a nightmare. A traditional update would have been catastrophic. Instead, we engineered a lightweight, modern wrapper around the legacy system.

This wrapper acts as both a proxy and a shield. It protects the previous IP while enabling synchronicity with modern tech. If IFS needs to change or move, the dependent systems don't flinch. They only talk to our modern API.

JLA Architecture Diagram

The "Juicy Bit"

Here is where the magic happens. We hosted the API in Azure, not on-premise. This significantly reduced the overhead of migration, allowing JLA to leverage the scalability and security of the cloud immediately.

By using an Azure VPN Gateway, we created a secure tunnel to the on-premise infrastructure. This enabled a seamless transition to the cloud with zero interruption to the daily workflow.

The Payoff

We delivered the durability and resilience of a traditional Enterprise Service Bus (ESB) without the bloat, licensing costs, or maintenance nightmares. Boom.

This wasn't just a fix; it was the first production project JLA deployed to Azure, paving the way for a trusted cloud future. We built a platform that adapts as fast as JLA grows.

 

  • 3 Critical Systems fully integrated.
  • 1.5 Million+ Assets transferred.
  • 100% Accuracy on known entities transferred.
  • 40+ Endpoints mapped.

 

JLA is no longer just "managing" their systems; they have a scalable, future-proof network ready for whatever comes next.