The Data Arch · From Pipelines to Platforms
I help experienced data engineers become the architects the AI era needs.
I’m Nitesh Sharma. I design enterprise-scale data platforms on Azure and AWS for banks, healthcare providers, and public-sector clients—the kind where getting it wrong means a regulator calls.
From support to architecture
Twenty years ago I started in support and recruiting. Today I design enterprise-scale data platforms across Azure and AWS for banks, healthcare providers, and public-sector clients.
Becoming an architect isn’t about knowing more tools. It’s about judgment—which trade-off to make, how to defend a decision, and how to tie a pipeline to a P&L line.
Outcomes over tool lists
A few things I’ve built—and the numbers behind them
- £53K/yr saved by automating regulatory reports at a UK building society
- £40K/yr cut through licensing rationalization
- 30% faster report execution through query and stored-procedure optimization
- Metadata-driven ingestion frameworks that cut new-source onboarding by 20%
- On-prem to cloud migrations (6R’s / TIME) across BFSI and healthcare
Why The Data Arch
I write here at The Data Arch for engineers growing into architecture: practical lessons about platform decisions, trade-offs, and the outcomes behind the design.
I’m also building ArchitectLab, a community for data engineers who want to grow into architects.
ArchitectLab · Coming Soon
The Data Arch Weekly
One practical lesson a week on becoming a data & AI architect — trade-offs, decisions, and the numbers behind them. Subscribe and get The Data Engineers’ Field Guide free.
Have an architecture challenge?
Let’s discuss the decision you’re trying to make and the outcome you need.