Insights: case studies3 studies
Every case study here covers a product we own. Client engagements carry confidentiality, so the only work we can document at the level of architecture decisions is our own.
Client case studies are published only with written permission, as set out in our confidentiality terms.
Case studies
Each study covers one product from context through to the decisions we would defend in a review. Where a decision has since looked wrong, we leave it in the study.
What a study contains
Each study is written for an engineer deciding whether our judgement is worth buying, so the rejected options matter as much as the shipped ones.
What existed before, who it was failing, and why the obvious solution had not already been built. Written so someone outside the sector can follow it.
The specific technical and commercial constraints that made the work hard, written clearly enough that you could disagree with our reading of them.
Every material call includes the alternative we turned down and why.
Described in words where no measurement exists yet, and in numbers where it does. Market figures are published with their source.
Related pages
Articles cover narrower technical ground. The products page covers the products themselves. The principles explain why the decisions above went the way they did.
Notes on architecture, AI, cloud and delivery.
Aurelia, Voyazio and AxleOne: stage, sector, model and availability.
The eight principles behind every decision in these studies.
Decision records are a deliverable on every engagement. Send us a brief and the first one arrives with the architecture note.