Software architecture and legacy systems
Architecture decisions that move revenue and risk: replacing a legacy system without a rewrite, choosing a content platform, and getting a payments ledger right.
The Strangler Fig Pattern Replaces a Legacy System Without a Rewrite
The strangler fig pattern replaces a legacy system one piece at a time, with the old system staying live as the fallback. Tests, not a launch date, decide when each piece is safe to switch over.
Your CMS Architecture Is a Revenue Decision, Not a Content One
A content-management system (CMS) reads like an editorial choice, but its architecture decides revenue: whether rankings survive a migration, whether the page appears without waiting for the ad auction, and whether you can switch back if launch goes wrong.
What a Fintech App Actually Costs Is the Reconciliation Logic, Not the Screens
Cost estimates for fintech products spend their time on features and compliance categories. The part that actually blows budgets — making sure two concurrent payment requests can never double-charge the same account — rarely gets a line item at all.