Why You Should Never Use a Database as an API
TL;DR: Sharing databases across team boundaries bypasses service interfaces, turning database schemas into public APIs. This tightly couples services, halts schema migrations, and stalls development.

Search for a command to run...
Articles tagged with #softwarearchitecture
TL;DR: Sharing databases across team boundaries bypasses service interfaces, turning database schemas into public APIs. This tightly couples services, halts schema migrations, and stalls development.

TL;DR: Conway’s Law states that system architectures inevitably mimic the communication structures of the organizations that build them. If you do not actively design your team boundaries and communic

Conway's Law states that an application's architecture and user interface will inevitably mimic the communication structures of the organization that built it. If your teams work in silos with high co

Quick Answer: When building an e-commerce system, never use today's exchange rate to calculate the value of past transactions. Currency values fluctuate daily. To keep financial analytics accurate, yo

Quick Answer: Code is "correct by coincidence" when it relies on duplicated, fragile details—like matching magic strings—that just happen to align perfectly to make the application work. Code is "corr

Quick Answer: Never use floating-point numbers to represent money in software. Because floating-point math cannot perfectly represent base-10 decimals, it introduces microscopic inaccuracies that comp
