Fourteen years building the data foundations high-scale systems depend on. I architect distributed database platforms, eliminate operational toil through automation, and turn hard technical problems into measurable business outcomes.
Led the migration of one monolithic MongoDB cluster (96 cores, 768GB RAM) into 65 right-sized clusters segmented by customer tier. Zero customer downtime across 8 months. $350,000 saved annually. Recognised with the company Thank You Award.
Full database estate recovery after AWS ME-Central-1 went completely offline during the Middle East conflict. Navigated UAE Central Bank data-residency constraints under emergency conditions. Database restore in 5 hours; back online before the banks were.
End-to-end automated database scaling: CloudWatch → SNS → SQS → rolling node upgrades with health-check validation at every step. Zero application impact. The on-call engineer became a notifier, not an actor.
Subject-matter expert for 1,000+ node Cassandra and MongoDB environments across multi-data-centre, multi-region private cloud, at global financial transaction scale.
Built a self-service portal at Visa: developers request environments through a UI, automation provisions them, and TTL auto-decommission cleans them up. The DBA bottleneck was removed from the developer workflow entirely.
MongoDB Certified DBA · MongoDB Certified Atlas Administrator · MongoDB Certified Associate Data Modeler · Apache Cassandra 3.x Administrator (DataStax).
mtools was brilliant, and its log tools never learned to read the JSON log format MongoDB introduced in 4.4. So I created the replacement.
mdbkit is an offline toolkit for MongoDB structured logs: slow-query analysis, deterministic index advice, incident triage and FTDC decoding, from the terminal, for MongoDB 4.4 through 8.0.
The part I care most about: it never connects to your database. No driver, no URI, no network code anywhere in it. Zero runtime dependencies, nothing in the supply chain but the Python standard library. It reads files, it is strictly read-only, and where an action would help it prints the command for you to review and run yourself. The README shows you how to verify all of that in a minute with grep and strace.
And when it recommends an index, that advice is rules, not AI. The same log always produces the same recommendation, with the evidence it reasoned from, a confidence level, and how to validate it. It says candidate, never command, and it will never tell you to drop an index.
Fourteen years of database engineering taught me how systems behave under real load. I apply the same rigour to AI, building agents that solve my own problems, and bringing AI-native workflows into how I engineer, architect, and operate data platforms.
Your AI is describing a MongoDB that no longer exists. It is not lying to you. It is describing roughly 4.2, because that is where the internet's supply of MongoDB blog posts is centred. Learn to read the plan, and the model stops being a confident guesser and becomes a very fast reader, which is what it is actually good at.
Built on depth, not just breadth. Fourteen years at the intersection where databases meet business outcomes.
From classified government networks in Abu Dhabi to FinTech platforms processing millions of transactions, from 1,000-node Cassandra clusters at Visa to 65-cluster migrations at high-growth SaaS, I have operated in environments where database failures are not an option. Today I lead data services engineering at IG Group, a global FinTech with a fifty-year history and operations across eighteen countries.
My approach is simple: understand the business problem first, then select the right technology. I have worked across MongoDB, Cassandra, Oracle, PostgreSQL, ClickHouse, Aurora, MySQL, Redis, Neo4j, and SQL Server, self-managed and cloud-native. Each has its place. The skill is knowing which place.
I also own the cost and vendor decisions that come with the platform. I have run multi-year TCO analyses: negotiating tooling contracts, weighing managed services against self-managed infrastructure, and making the call that saved real money without compromising reliability. Platform ownership is as much a commercial discipline as a technical one.
And I write and ship in the open. mdbkit is on PyPI under MIT, Tales from Production runs on dev.to, and I co-lead Namma MUG in Bengaluru after founding the MongoDB Abu Dhabi User Group. None of it depends on where I work.
Across sectors: FinTech · SaaS · Banking · Trading · Gaming · Government · Social Media · Payments
The MongoDB Community Creator program selects fewer than 50 engineers globally each year. I am one of them, among the very few from India and the UAE. There was a MongoDB user group in Dubai and nothing in Abu Dhabi, so I was asked to start one. I founded it and ran its first session as its founding leader. I now co-lead Namma MUG in Bengaluru, speak at community and industry events, and publish regularly on database architecture, performance, and AI-native data systems. Community building is not something I do for recognition. It is how I stay sharp.
I co-lead Namma MUG, the MongoDB User Group in Bengaluru, and founded the MongoDB Abu Dhabi User Group before that. I speak at community and industry events on MongoDB architecture, query planning, and AI-native database operations.
Short write-ups of real database incidents from production. Three to five minutes each. No hero stories, no vendor pitches, just what actually broke and how we read our way out of it. Published on dev.to.