About
Fifteen years in database engineering, taught me that the platform is the product.
I'm Mahesh Gupta, an Associate Director and Principal Database Engineer working in enterprise data platforms for capital markets. My background is SQL Server and enterprise database administration — my current work is architecture: data strategy, cloud infrastructure, cost governance, and the standards that let a database organization operate at scale.
How I think about the work
Most database problems that reach an architecture review aren't really database problems — they're cost problems, governance problems, or scale problems wearing a database costume. I spent the first decade of my career solving the technical layer. The last several years have been about solving the layer above it: designing systems and standards that keep the technical layer healthy without needing me in the room.
That shift shows up in three areas I keep coming back to:
- FinOps as an engineering discipline, not a monthly report. Cost governance works when it's built into the architecture — tagging taxonomies, ownership accountability, automated findings — not bolted on after the bill arrives.
- Migration as risk management. Moving a mission-critical database estate to the cloud is less about the target architecture and more about sequencing the move so nothing mission-critical is ever the experiment.
- Standards as leverage. A review board and a published deployment pattern do more for platform reliability, at scale, than any individual engineer's vigilance.
Background
I hold AWS Solutions Architect and Microsoft Azure certifications, and completed a postgraduate program in Generative AI and Machine Learning to bring that lens into how I think about the next generation of data platforms — particularly around applying internal LLM tooling to operational findings and executive reporting.
Before moving into architecture, I spent years as a hands-on SQL Server DBA and Lead Database Engineer, running production database environments for enterprise-scale platforms — the kind of work that makes you permanently allergic to elegant designs that don't survive a 2 a.m. page.
Outside the day job
I write here about the FinOps, migration, and architecture problems I run into — mostly as field notes, generalized enough to be useful to anyone tackling the same problem at their own company.