Lead Architect

Re-Architecting 411 to Deliver an 11.1x Search Speed Breakthrough

This was a legacy rescue mission with one non-negotiable outcome: transform a crash-prone platform into an 11.1x faster search system while restoring runtime stability at peak load.

2.0s -> 0.18sSearch Response Time
11.1x fasterSpeed Improvement
9New Microservices
Crash risk controlledStability Outcome

411 Local Search Corp

A large-scale directory search platform optimized for high-volume data and responsive query performance.

411 Local Search Corp operates in a market where speed and uptime are the product. The legacy application was degrading under load and trending toward platform-wide instability during peak traffic.

I led the architecture diagnosis and redesign strategy with a clear priority: prevent crash scenarios first, then unlock performance and scalability at the system level.

The modernization delivered both outcomes, with the defining result being a jump from 2.0s to 0.18s response time (11.1x faster), while establishing a stable runtime posture for long-term growth.

Challenge Landscape

  • Search queries averaged 2 seconds and spiked to 10 seconds under stress.
  • Result sets included duplicates and irrelevant records that eroded trust.
  • Roughly one-third of existing data required cleaning and treatment.
  • Infrastructure spending was high and operational efficiency was low.
  • Monolithic architecture prevented effective horizontal scaling.
  • Manual delivery workflows slowed release cycles and increased human error.

Strategic Response

  • Executed a full architecture transition from monolith to SOA and microservices.
  • Implemented a custom API gateway to centralize traffic management, authentication, and routing control.
  • Migrated search from MySQL to ElasticSearch and applied advanced relevance tuning features.
  • Detached frontend channels from backend services and rebuilt frontend experience for speed and maintainability.
  • Containerized the platform and deployed on Kubernetes to improve resilience and scalability.

Key Architectural Decisions

  • Architectural migration from monolith to SOA and microservices.
  • Introduced 9 new microservices with custom APIs using SOAJS.
  • Built a custom gateway for traffic distribution, authentication, and cloud awareness.
  • Migrated data stack from MySQL to ElasticSearch with fuzzy, phonetic, and bilingual stemming support.

Measured Impact

  • Delivered the core business KPI: search response time improved from 2.0 seconds to 0.18 seconds (about 11.1x faster).
  • Stabilized the platform and eliminated crash-prone peak-hour behavior.
  • Improved search relevance and removed duplicate result sets.
  • Significantly reduced infrastructure cost through architecture and delivery modernization.

When a legacy platform starts collapsing under load, I lead the modernization that produces hard outcomes, including 11x-class performance gains, not just architectural slideware.

M360API

A modernization platform that lets companies extend legacy systems without discarding years of engineering investment.

>