Why Historical Records Need Snapshots, Not Live References A customer places an order on Monday. On Friday, they update their delivery address. Nothing unusual has happened. Yet when support opens Monday’s order, the system now shows Friday’s address. The database is...
How to Model Approval Workflows in a Database Without Boolean Chaos A supplier application has been approved. Then its bank details change. Is the supplier still approved? The answer sounds like a business-policy question, but it quickly becomes a database design...
When Reference Data Changes: Designing Database Codes That Preserve History A shipping database contains an order from 2022 with the delivery method EXP. Today, EXP means “Express Delivery — next business day.” But in 2022, the same code meant “Express Delivery —...
When Your Data Sources Disagree: Designing a Database That Preserves the Truth A company is preparing to replace three old systems with one new database. The CRM says customer 1842 is called Northstar Labs. The billing system says Northstar Laboratories Ltd. A...
External IDs Are Not Your IDs: Modeling Identity Across Systems A backend team adds one column to the customer table: stripe_customer_id Six months later, another integration arrives: hubspot_contact_id Then the company migrates its support platform, imports customers...
Recent Comments