All work

Case study 03 / 06

Enterprise modernization · Next.js · .NET · Performance

Motor Renewal Modernization

Primary hands-on engineer migrating motor renewal and two-wheeler journeys from Angular to Next.js, and moving business rules into .NET services that return frontend-ready data.

Role
Primary hands-on engineer · guided interns
Company
ICICI Lombard
Stack
  • Angular
  • Next.js
  • React
  • TypeScript
  • .NET
  • ASP.NET Core
  • EF Core
  • PostgreSQL
  • Oracle
Motor renewal modernization: before, an Angular client called several services itself; after, a Next.js client calls one frontend-ready .NET API that talks to the core policy system directly. Lighthouse rose from 37 to 93 on the migrated journey.BEFOREAngular clientBUSINESS RULES IN UISERVICE 1SERVICE 2SERVICE 3SERVICE 4IntermediaryXML CORE INTEGRATIONAFTERNext.js clientSSR / SSGASP.NET Core APIFRONTEND-READY RESPONSESCore policy systemJSON (V2.0) SERVICESPostgreSQLMIGRATED FROM ORACLE93LIGHTHOUSE · FROM 37~14% FEWER API CALLS~27% FASTER LOADMIGRATED RENEWAL JOURNEY
Simplified, public-level view of the documented architecture

01

Overview

A modernization of legacy motor-insurance renewal journeys and their supporting services: Angular pages rebuilt in Next.js, and frontend-heavy business logic moved into backend services.

02

Context

The legacy journeys asked the browser to call several services just to work out simple flags and statuses, and the core system exchanged XML that had to be converted before reaching customers.

03

Problem

Make the renewal journey faster and simpler to evolve by modernizing the frontend and giving it APIs shaped for what the screen actually needs.

04

Constraints

  • A legacy enterprise codebase with live customer traffic.
  • Existing integrations with the core policy system and payment gateway.
  • Work delivered by a small team — me with a few interns.

05

My contribution

  • Primary hands-on engineer on the Angular-to-Next.js migration of motor renewal and two-wheeler journeys, guiding interns.
  • Designed frontend-ready ASP.NET Core APIs that move business rules and multi-service orchestration from the client into the backend.
  • Integrated new flows directly with the core policy system, removing intermediary service hops.
  • Contributed to replacing XML core integration with the core system's JSON (v2.0) services.
  • Contributed to the Oracle-to-PostgreSQL migration (EF Core) — live for RYD Raksha and the new two-wheeler flow.
  • Contributed to the renewal payment gateway integration.

06

Architecture

Move orchestration from the browser to the backend

Before: the Angular client called several services and computed flags itself. After: the Next.js client calls .NET endpoints that already return what the screen needs, and those services talk to the core policy system directly.

  • Frontend: Next.js (SSR/SSG where useful) replacing Angular pages.
  • Backend-for-frontend style ASP.NET Core APIs returning frontend-ready responses.
  • Direct core-system integration instead of intermediary hops.
  • Core-system JSON (v2.0) services replacing XML.

07

Decisions & trade-offs

Frontend-ready API responses
One call that returns the decision is faster and safer than the browser stitching together several services to compute it.
Business rules in the backend
Rules live in one place, are testable server-side, and no longer ship to every browser.

08

Impact

  • 37 → 93

    Lighthouse score

    Migrated renewal journey

  • ~27%

    Faster page load

    Migrated renewal journey

  • ~14%

    Fewer API calls

    Renewal journey, after moving orchestration to the backend

  • Metrics apply to the specific migrated renewal journey, not every flow.

Described at a public level — no confidential company, customer or system details.