Single Source of Truth (SSOT): One Place for Every Fact

WHY IT EXISTS Without a central authority, data gets copied across systems. When one copy changes, the others become stale and incorrect. This leads to conflicting reports, wrong decisions, and bugs. For example, does the sales team or the support team have the customer's real phone number? SSOT was created to solve this ambiguity and enforce data consistency.

THE MENTAL MODEL SSOT is the practice of structuring systems so every data element, like a customer's email, is owned and updated in exactly one place. All other systems that need this data must refer to or query this single source. It's the difference between emailing report_final_v3.docx around and sharing a link to a single, live document where all changes are centralized.

HOW IT WORKS SSOT is an architectural principle, not a single technology. It's implemented by designating a specific service or database as the "master" for a piece of information. For instance, a UserService might be the SSOT for user profiles, while a BillingService is the SSOT for payment information. When a ShippingService needs a user's address, it must ask the UserService; it is not allowed to store and maintain its own copy. This is enforced through API contracts and system design.

WHEN TO USE IT Use SSOT in any system where data consistency is critical, especially in microservices architectures where different services need to agree on shared data. It is essential for financial reporting, regulatory compliance, and any scenario where conflicting data could cause serious business or operational problems.

WHEN NOT TO USE IT Strictly enforcing SSOT can create performance bottlenecks or single points of failure. If the UserService is down, no other service can get a user's address. For this reason, systems often use caches or read-replicas. The key is that these are explicitly treated as temporary, potentially stale copies, not as alternative sources of truth. The architectural discipline remains.

ONE CANONICAL EXAMPLE A company's Human Resources Information System (HRIS) is the SSOT for employee data like name, title, and start date. The payroll system, IT provisioning tools, and the company directory all pull from the HRIS. If an employee is promoted, the change is made once in the HRIS, and all downstream systems reflect that update. No one has to update three different spreadsheets.