Every cloud provider has one. Every major consultancy sells one. Every conference talk ends with one on the final slide. Reference architectures are everywhere. And most of them are making your platform worse. The problem with reference architectures A reference architecture is a idealised blueprint for how a system should be structured. In theory, it gives teams a proven starting point, reduces decision fatigue, and encodes best practices from organisations that have already solved the hard problems. In practice, most organisations use them wrong. They treat the reference architecture as the destination rather than the starting point. They adopt the full stack because the diagram says so, not because they have validated that each component solves a problem they actually have. They optimise for looking like the reference architecture rather than optimising for what their developers actually need. The result is platforms that are architecturally impressive and operationally painful.…