Selected Work

The CRM had grown organically over several years into a tightly coupled system. Frontend and backend changes were deeply intertwined, deployments were risky, and performance issues were increasingly common under production load. A full rewrite was not an option due to active users and continuous business requirements.

Synchronous workflows caused cascading failures during traffic spikes and third-party outages. A single slow or failing dependency could block user-facing requests and leave transactions in inconsistent states.

Search queries across large relational datasets were slow and limited in functionality. Users experienced lag when filtering or searching, and complex queries placed heavy load on the primary database.