The Architectural Evolution (2006 — Present)
I view my career not just as a list of jobs, but as a series of architectural shifts. Each era represents a new challenge in how we handle data and scale.
Scaling the Model Context Protocol (MCP) to bridge the gap between LLMs and secure Data Lakes, enabling AI agents to interact with Petabyte-scale datasets safely.
Bridging the gap between Data Warehouses and Data Lakes. Implementing open table formats for high-performance ACID transactions on object storage.
Pivoted to real-time event-driven architectures and distributed computing to handle high-velocity streaming and Petabyte-scale challenges.
Integrated predictive power into applications, moving from standard logic to Deep Learning and Graph-based relationship modeling.
Led the migration from modular application to microservices.
Led the migration from on-premise hardware to elastic cloud environments, optimizing for high availability and global scale.
Transitioned from rigid monoliths to modular "Shared Nothing" architectures. Focused on decoupled data access and the early Spring ecosystem to improve team velocity.
Adopted the Spring ecosystem to handle complex enterprise requirements and "Rich Internet Application" (RIA) frontends.
The foundation: Building robust, server-side rendered web applications with core Java and relational database design.
Perspective: Coming from an Electrical and Electronics Engineering background, I’ve always viewed software through the lens of signal processing and circuit efficiency. This “low-level” understanding helps me optimize Big Data pipelines where every byte and millisecond counts.