esb

Work / case studies

Problems I've owned, end to end.

Most of my work lives inside a production communications platform, so the code isn't public — but the problems, decisions and outcomes are.

Real-time AI communication layer

A Java WebSocket API layer connecting two core platform components to an OpenAI-integrated AI connector, with gRPC for internal service-to-service traffic.

The problem. A speech-to-speech product needed real-time, bidirectional interaction between existing platform components and a new AI connector — without compromising the platform's security posture.

What I built. A WebSocket API layer in Java that streams between two core components and an OpenAI-integrated connector, with gRPC handling internal communication. The channel is secured end to end with WSS and JWT-based authentication.

Outcome. Low-latency, authenticated, bidirectional messaging that let the AI connector plug into the platform as a first-class service.

JavaWebSocketgRPCWSSJWTOpenAI API

JDK 11 → 17 / 21 migration

Led the migration of a core Java communications framework to modern JDKs, then hunted down and fixed the critical failures it surfaced across the service fleet.

The problem. A core communications framework spanning 15+ modules was pinned to JDK 11, blocking security updates and modern language features.

What I did. Led the upgrade to JDK 17 and 21, resolving cross-version compatibility issues module by module. After rollout, I diagnosed and fixed critical post-migration failures in session management, identity and monitoring services.

Outcome. 15+ modules migrated and 25+ microservices restored to full stability on the new runtime.

Java 17Java 21Spring BootMavenRoot cause analysis

Identity & certificate management redesign

Reworked how the platform handles identities and certificates, fixing a long tail of failing cases and an expiry bug while upgrading cryptography.

The problem. Identity and certificate handling had 25 failing cases, including a certificate-expiry issue, and some cryptographic algorithms fell short of enterprise standards.

What I did. Redesigned the identity and certificate management flow and upgraded the cryptographic algorithms in use.

Outcome. 15 of 25 failing cases fixed, the expiry issue resolved, and the platform aligned with enterprise security standards.

SecurityTLSCertificatesCryptographyJava

Infrastructure validation framework

An automation framework that cross-checks REST APIs, YAML configs and management beans so environments can be validated without manual inspection.

The problem. Validating infrastructure meant manually comparing what REST APIs reported against YAML configuration and runtime management beans — slow and error-prone.

What I built. An automation framework that pulls all three sources and compares them, flagging drift automatically.

Outcome. Manual validation effort cut by over 30%.

AutomationRESTYAMLJMXRobot Framework

Idempotent REST APIs & CI stability

APIs designed so retried or duplicated requests are processed safely, backed by JUnit/Mockito coverage and a stabilized Jenkins pipeline.

The problem. In a distributed system, clients retry. Without idempotency, retries create duplicate side effects.

What I did. Built idempotent REST APIs so repeated requests are processed safely, wrote JUnit and Mockito tests for the features I delivered, and resolved Maven build issues across 5 project suites.

Outcome. Correct behavior under retries and a stable Jenkins CI pipeline for the team.

RESTIdempotencyJUnitMockitoJenkinsMaven

Speech-to-speech platform design

Co-led the design of a core platform component and defined the reliability KPIs used to track it across the system.

The problem. A new speech-to-speech product needed a core platform component, and a way to know whether it — and everything around it — was healthy.

What I did. Co-led the component design and defined KPIs for 10+ components to track performance and reliability.

Outcome. A shared, measurable definition of "healthy" for the product's critical path.

System designReliabilityObservabilityKPIs

Retail customer management system

An internship project built end to end — backend services and REST APIs for managing customers in retail and shop use cases.

The problem. Retail and shop owners needed a simple system to manage customers.

What I built. Core backend services and REST APIs in Java and Spring Boot on MySQL, owning the work from design through implementation and validation.

Outcome. A working system and an architecture review presented to senior engineers.

JavaSpring BootMySQLREST APIs

Want the deeper technical story behind any of these?

Ask me about it