Your monolith is slowing you down. Deployments are risky, features take too long, and one bad change cascades everywhere. I decompose monolithic APIs into clean, independently deployable microservices in 2 weeks — with working code, not just a diagram.

Engineering teams and technical founders dealing with:

A monolith that's become painful to deploy or scale

API endpoints that are slow, brittle, or impossible to test in isolation

A codebase where every change risks breaking something unrelated

Legacy REST APIs that need to evolve into something modern (GraphQL, event-driven, etc.)

I've done this in production at Ellucian — decomposing a platform into 6 TypeScript/Node.js microservices with event-driven communication, serving thousands of institutions. I know where service boundaries should go, how to handle data ownership between services, and how to migrate without downtime.

Map your current API surface, data flows, and coupling points

Identify natural service boundaries based on domain logic (not just endpoint grouping)

Design the target architecture: service contracts, data ownership, communication patterns

Deliver: architecture decision record + migration plan

Extract the highest-value service into a standalone, deployable unit

Set up inter-service communication (events, REST, or GraphQL federation)

Write tests, deployment scripts, and monitoring hooks

Deliver: working service, deployment guide, and roadmap for remaining extraction

1 fully extracted, production-ready microservice

Architecture doc covering all remaining services and migration sequence

Test suite with contract tests between services

AWS deployment configuration (ECS or Lambda)

1-hour walkthrough + 2 weeks post-delivery support

Node.js, TypeScript, Express/GraphQL, MongoDB/PostgreSQL, AWS (ECS, Lambda), Docker, Terraform, Jenkins/GitHub Actions