Case studies

Case studies written as architecture notes.

Systems and migrations documented through constraints, tradeoffs, and outcomes.

Evolving/2026

abhish3kk.in — A Low-Maintenance Engineering Publishing Platform

Three iterations, each with the same failure pattern: the setup was easy, the maintenance won. The fourth version strips the infrastructure to almost nothing — MDX files in git, Zod schema validation at build time, Azure Static Web Apps for hosting. No VPS, no CMS, no ops overhead.

Static sitesContent systemsPublishing infrastructureOperational simplification
Shipped/2026

Angular Migration Across Shared Microfrontends

How we migrated a tightly-coupled microfrontend platform from Angular 13 to 18—with ag-Grid 29 to 32 in tow—while preserving rollback safety and coordinating sign-off across multiple downstream teams.

Microfrontend ArchitectureFramework MigrationRelease Engineering
Shipped/2026

Frontend Error Visibility Across Eight Microfrontends

Frontend errors were disappearing silently into the browser console with no record. We built a batched async capture pipeline across eight microfrontends — errors now land in MongoDB and incident triage is a query, not a call.

ObservabilityError TrackingMicrofrontend Architecture
Shipped/2026

Moving Validation Earlier Across a Multi-Repo Frontend Platform

Late-stage QA was the single validation point across multiple microfrontends — changes sat in the queue for days, and downstream instability made timing unpredictable. We introduced layered pipeline enforcement that cut feedback cycles from days to hours.

Delivery EngineeringRelease EngineeringTesting
Shipped/2026

SOAP to REST Migration with Production Validation

Trade retrieval was taking 2–5 minutes through a legacy SOAP service. We replaced it with a REST path, validated against live traffic in production, and kept SOAP as a hot fallback until confidence was established.

Service MigrationReliability EngineeringRollout Strategy
Shipped/2025

RepoFinder React

A focused GitHub repository search tool — built to work through state separation, API rate limits, and client-side deployment constraints.

Frontend architectureSearch and filteringAPI boundaries