In 4 months, we moved our core platform from a legacy setup to a cloud-native architecture with less operational friction.
Available · Q3 engagements
~/ Software systems that outlastscale withship faster thansurvive the next quarter.
Field notes and hands-on consulting. Mostly TypeScript, AWS, and the organizational shapes around them.
§ 01
Latest Posts and Notes
View All Posts Keeping a GraphQL BFF Standing When Its Dependencies Fall Over
A GraphQL gateway over many microservices is your highest-leverage and most fragile service. Resilience comes from connector isolation, batching, cost limits and degradation.
graphqlapi-gatewaybff +5
June 18, 2026 Development
Lambda Durable Functions vs Step Functions: When the Orchestrator Belongs in Your Code
Lambda durable functions put the orchestrator in your TypeScript. Reach for them when you own the whole workflow; keep Step Functions for cross-team state machines.
aws-lambdastep-functionsserverless +2
June 17, 2026 Cloud Computing
Code Architecture by Init Amortization: Lean on Lambda, Heavy Only When Earned
Match architecture weight to each runtime's init-amortization: lean handlers on single-purpose Lambda, more on a Lambdalith, full OOP/DI only on long-lived runtimes.
software-architectureaws-lambdaserverless +3
June 3, 2026 Cloud Computing
§ 02 · outcomes
Selected Outcomes
With a focused AWS and serverless redesign, we reduced annual infrastructure spend by around $200K.
§ 03 · services
How I Can Help
Focused support for architecture and delivery decisions.
Architecture Review
I turn your current setup into a clear, practical technical direction.
Sharper technical decisions
Technical Advisory
Short, practical guidance for product and engineering teams.
Fast and focused feedback