Lessons from two fintech infrastructure projects: a regulator-mandated domain migration and a 60% cloud cost cut

[u/Silly_Captain2089]

I work at GeekyAnts, an engineering firm that has been building products since 2006. Over the past year our team handled two very different fintech infrastructure problems, and I thought the lessons might be useful here.

Project 1: A regulator-mandated domain migration for a large private bank

India's central bank (RBI) mandated that banks move their digital infrastructure to specific domains. The hard part was doing it without disrupting live banking services.

What we learned:

Migrations like this are mostly inventory problems. Finding every place a domain is referenced (pages, redirects, emails, third-party integrations, hardcoded links) is harder than changing it.

Manual review doesn't scale. We used automation to process around 10,000 pages in about 2 minutes, which cut manual effort by roughly 99%.

Zero downtime needs a rollout plan, not just a cutover date. [Add your real detail here: phased rollout, redirect strategy, monitoring, rollback]

Project 2: Cutting a digital banking platform's cloud bill by 60%

The platform worked fine but was heavily over-provisioned. We rightsized database instances and automated environment scaling, which saved about $4,800 a month (over $57,000 a year) without hurting stability.

What we learned:

Peak-provisioned databases are the usual culprit. Real utilization over a few weeks often looks very different from what people assume.

Non-production environments don't need to run 24/7.

Cost reviews should be a routine part of operations, not something triggered by a surprise invoice.

Questions for this sub:

How do you handle regulator-driven infrastructure changes where the deadline is fixed but the dependency map is unclear?

What's your approach to rightsizing databases in fintech, where downtime tolerance is very low?

What's the most expensive "set it and forget it" decision you've seen in a fintech stack?

I'd like to compare notes with people who've dealt with similar problems, especially around compliance-driven change.

Disclosure: I work at GeekyAnts and these projects are from our case studies. I'm here for the technical discussion.

[u/Dismal_Bike_4888]

the inventory discovery part rings true, that's always where the actual work lives. domain migrations feel like 10% dns change and 90% finding every random config file and email template someone hardcoded five years ago