AWS & Cloud · Financial Services

Serverless Core Platform Migration

Mid-size investment bank · US East Coast

55% infrastructure cost reduction
Mid-size investment bank · US East Coast

The challenge

The bank ran its core processing platform on a Java monolith deployed on 18 EC2 instances. Monthly infrastructure cost was $380,000. Deployments happened monthly at best — the release process took four days and required a weekend maintenance window. The engineering team was spending more time managing infrastructure than building features.

The approach

A previous migration attempt had been abandoned when the team discovered mid-project that two services had undocumented dependencies. Shelorve deployed CodeSight before any architecture work began, identifying sixteen undocumented integrations which were resolved before migration.

The monolith was decomposed into 34 Lambda functions using AWS CDK. DynamoDB replaced the session database. EventBridge replaced the internal event bus. External integrations were rebuilt as API Gateway endpoints.

The outcome

Infrastructure cost dropped from $380,000 to $171,000 monthly — a 55% reduction. Deployments moved from monthly to daily, and the release cycle reduced to 22 minutes with CI/CD automation.

Technology

Lambda · CDK · DynamoDB · EventBridge · CodeSight™

How long did the migration take?

The full migration took seven months from CodeSight discovery through to production cutover. The CodeSight phase was four weeks. Architecture design was three weeks. The build and phased migration was five months.

Was there any downtime during the cutover?

No planned downtime. The cutover used traffic shifting — Lambda functions received an increasing percentage of traffic while the monolith remained live. The monolith was decommissioned after 30 days of parallel running with zero incidents.

How were the external partner integrations handled?

Each of the sixteen external integrations was rebuilt as a documented API Gateway endpoint with full contract testing before the corresponding monolith service was retired. External partners were notified and provided test environments four weeks before cutover.

Work With Shelorve

This could be
your story.

Tell us what you are trying to fix. We will tell you whether Shelorve is the right partner — and if we are not, we will tell you that too.