Performance audits, architecture reviews, and hands-on technical leadership. From someone who opens your codebase, not a slide deck. Also available as Fractional CTO →
How I help
Hands-on engineering, not PowerPoint consulting. Each starts with a free 30-minute scan.
Cut your cloud bill 20-50%. I find the waste and ship the fixes. Savings land on your next invoice.
Learn more →Slow app → fast app. Real results: 3s → 80ms response, 2× checkout conversion.
Learn more →Production AI, not demos. LLMs, RAG, and agents wired into your existing stack.
Learn more →Survive 10× traffic. Capacity planning, autoscaling, and architecture so launch day is boring.
Learn more →SOC 2, ISO 27001, GDPR. Technical controls and docs to pass the audit. From someone who ships in regulated SaaS.
Learn more →Book a free 30-minute call. We'll find your biggest bottleneck and I'll tell you exactly what I'd do.
Learn more →Also: Architecture Review, Senior Tech Advisory, CI/CD & Automation, Legacy Modernisation. Ask about any of these →
Results
A free PDF checklist covering the most expensive mistakes I see in cloud setups, and how to fix each one in under a day.
Senior hands-on help, not slide decks. I open your codebase, find the real bottleneck, and ship fixes with your team - in weeks, not quarters.
20+ years across backend, cloud, and IoT. Shipped at scale from early-stage startups to global enterprises. Oracle Certified Professional: Java SE 11.
When your system is slow, expensive, or fragile - I'm the engineer your staff lead calls.
Java, Kotlin, Python
AWS, Azure, DigitalOcean, Kubernetes, Terraform, bare-metal Linux
PostgreSQL, MySQL, Redis, MongoDB, Kafka, RabbitMQ (also: MSSQL, DB2)
Performance, DDD, Event-driven, CI/CD
Industries
IoT · Autonomous Logistics · GovTech · Fintech · Healthcare · Telecom
Practical guides on Java, Spring Boot, cloud architecture, and developer productivity.
Most teams reach for sharding years before they need it. There is a ladder of cheaper, lower-risk fixes that comes first, and the right rung depends on which bottleneck you actually have: read load, write load, or data size. Here is the ladder, from cheapest to last resort.
Both are excellent databases and for most SaaS workloads either one is fine. The honest answer: pick Postgres for greenfield, keep what you run well, and switch only for a reason you can name. Here are the few differences that actually decide it.
A government directive can now switch off your AI provider overnight - and pricing, deprecation, and policy could always do it. If a core feature depends on one model API you don't control, that's a single point of failure. Here's how to treat model access like any other supply-chain risk.
Most slow-query problems are not a missing index, they are the wrong index, or ten indexes nobody needs. Start from the query plan, build the index the query actually wants, and drop the ones taxing every write.
Book a free 30-minute call. We'll look at your biggest bottleneck and I'll tell you exactly what I'd do - no strings attached.
