01Platform & Middleware
- JBoss, WebSphere, WebLogic, Tomcat
- Apache HTTPD, IHS, OHS, JBCS
- mod_jk, mod_proxy, proxy balancer, mod_cluster
- MySQL, Oracle 12c/19c, MSSQL, PostgreSQL 16
Infrastructure & Platform Engineering
I design, run and harden infrastructure across Kubernetes, Azure and Java middleware — from disaster-recovery topology and DevSecOps pipelines down to the thread pools that decide whether a release holds under load.
About
I started in application servers and performance engineering — JBoss, WebLogic, WebSphere, Tomcat and Apache HTTPD — where a badly sized thread pool is the difference between a quiet release night and a war room. That grounding still shapes how I approach platforms: measure first, model the queue, then change one thing.
Today I lead infrastructure delivery for core banking implementations, covering Azure administration and migration, Kubernetes and OpenShift adoption, Jenkins-based DevSecOps pipelines with quality and vulnerability gates, and disaster recovery across on-premises and cloud estates. I have led an eleven-person platform team through implementations for banks across India and the Middle East.
The work I enjoy most sits where automation meets evidence: pipelines that fail for the right reasons, dashboards that answer a question, and rollouts that can be reversed in seconds.
Expertise
From the operating system up to the delivery pipeline.
Writing
Longer pieces on the systems I work with day to day.
Rolling updates tell you a pod is healthy, not that a release is good. This walks through progressive delivery on Kubernetes — replica-ratio canaries, ingress weighting, service-mesh traffic splitting and automated analysis with Argo Rollouts — plus the failure modes that catch teams out.
Read the articleHow the worker MPM actually allocates processes and threads, how to size MaxRequestWorkers from measured throughput instead of guesswork, how to read the scoreboard, and how to align the web tier with the backend pool so a slow application never becomes a queue collapse.
Read the articleA walk down the Catalina stack — Server, Service, Connector, Engine, Host, Context, Wrapper — following a single HTTP request from the acceptor socket through the poller, the pipeline of valves, the classloader hierarchy and into your servlet, then back out.
Read the articleTrack record
Contact
Consulting, platform reviews, performance investigations or a full-time role.