COMMERCE ARCHITECTURE AT SCALE
Design notes on commerce platforms that stay simple as they grow.
Large commerce platforms get harder to change as they grow. The reason is rarely the code. It is usually the boundaries — between systems, between teams, and around the rules a business cannot change.
These notes work through those problems: how to place the boundaries, what each choice buys you, and what it costs. The examples come from Salesforce Commerce Cloud, where I work day to day. The thinking applies to any commerce platform of this size.
Written for two readers. If you build these systems, each study goes into the mechanics and the trade-offs. If you plan or run them, each study opens with a short, plain summary of what the decision gives you and what it puts at risk.
Long-form design studies. Each one works through a real problem, the options, and the trade-offs.
Read →LibraryShort patterns and decisions. What each one solves, and when not to use it.
Read →AI for ArchitectsUsing AI to make architecture writing consistent, without handing over the judgment.
Read →AboutHow I think about this work.
Read →