Consulting Cloud Native Architect - FinTech. 21+ years making enterprise systems fast, resilient and cost-efficient. ex-Mastercard.
-
🔭 Currently working on Modernizing a 20-year-old platform and its engineering org with AI-augmented software engineering practices
-
🌱 Currently exploring How AI-native engineering can bake architecture, performance engineering, resiliency, and cost-efficiency into building high-throughput / low-latency systems
-
💼 Available for:
- Fractional CTO role
- Hands-on architectural consultancy (greenfield & modernization initiatives)
- AI-augmented software engineering practices
- Performance Engineering / Optimization (Application, Database, Infrastructure)
- Architecture Diagnostic Sprints
- Security audit and remediation
-
📝 I write regularly at dhaval-shah.com
-
💬 Ask me about Distributed Systems Architecture, Performance Engineering (application / DB / infrastructure), Cost optimization, AI augmented software engineering
-
📫 Reach me: dhaval@dhaval-shah.com
-
📄 Profile: Consulting Cloud Native Architect
- 🔗 se-ai-templates — Reusable AI-augmented prompt templates for ADRs, Performance Engineering, DB Optimization, SRE, FinOps & Cost Optimization
- 🔗 Beyond Throughput with Virtual Threads — JDK vs. Spring Reactor virtual threads, real throughput data
- 🔗 PostgreSQL optimization study — 10M-row payment dataset, EXPLAIN ANALYZE and optimization walkthrough
- 🔗 IRIS cross-cloud file transfer — AWS S3 → Azure Blob, Spring Boot/Project Reactor, Adaptive concurrency
- 🔗 Billion User Trap — the pagination mistake that can take down your database
- Three Azure Cost Leaks - And the Analysis Process That Found Them
- A Black Friday Incident Took 9 Days to Resolve - Here's the Process That Would Have Changed That
- Same JSON Storage Problem, Different Database - What Postgres Does Differently
- Billion User Trap - The Pagination Mistake That Can Take Down Your Database
- The GC Summary Report Wasn't Wrong - It Just Wasn't Complete
