Vinoth Kumar Kasi
Senior Oracle integration engineer — I architect OIC and Fusion landscapes for Fortune 500 estates
For 11+ years I've architected and operated Oracle integration systems for Fortune 500 companies — most recently as the L3 escalation engineer for a 1,500+ integration OIC estate across six production servers. I lead ERP-migration integration workstreams, design reusable frameworks that outlast the teams that built them, and increasingly build AI tooling into that practice.
About
The integration half of my work is 11 years deep: Oracle Integration Cloud, SOA/OSB, Fusion middleware, multi-wave ERP migrations, and the production escalations nobody else can reproduce. I care about the unglamorous parts — error handling, monitoring, cost attribution, and frameworks that survive the teams that built them.
The AI half is newer and deliberately scoped. I build small, read-only tools that put language models to work against real systems — like an MCP server that answers OCI metrics questions in plain English. The human owns the architecture; AI accelerates the build. I write up the design decisions as I go.
Selected work
Fortune 500 OIC estate — L3 escalation & architecture
Senior Oracle SME for a 1,500+ integration OIC estate across six production servers and three business verticals. Diagnosed a critical WMS→ERP performance issue mis-attributed to OIC — ruled out the integration layer, isolated VPN latency, restored baseline processing. Across earlier engagements: architected E-Business Suite → ERP Cloud migration landscapes and a reusable PL/SQL framework over DBMS_CLOUD that was adopted across customer projects.
oci-metrics-nl-mcp
AI tooling aimed straight at my own domain: an MCP server that lets Claude — or any MCP client — query Oracle Cloud Infrastructure metrics in plain English. Ask "which integration is burning through our message packs?" and get a ranked answer with a chart, instead of six clicks in Metrics Explorer. Read-only by construction, enforced at the IAM layer.
filet-file-wallet
An iOS file-transfer app, built to test a hypothesis: with the right discipline, does an experienced engineer's judgment carry into an unfamiliar stack? Your iPhone runs a local web server; any device on the same Wi-Fi transfers files through a browser — no app, no account, no cloud. Streams multi-GB files at constant memory (111 MB peak on a 4 GB download). AI wrote the Swift; the architecture, benchmarks, and verification were mine. Write-up on the blog.