DRY vs SOA
DRY (Don't Repeat Yourself) and SOA (Service Oriented Architecture) both come up in technology conversations and get confused. Here's the plain-English difference, side by side, so you can use each one with confidence.
The key difference: DRY refers to don't repeat yourself, while SOA refers to service oriented architecture — they describe different things even when they show up in the same sentence.
DRY — Don't Repeat Yourself
Principle that every piece of knowledge should have a single, unambiguous representation in a system. DRY done badly creates the wrong abstractions — duplication is cheaper than the wrong coupling.
SOA — Service Oriented Architecture
Architectural style where business capabilities are exposed as loosely coupled, reusable services. SOA was the precursor to microservices — same idea, heavier ceremony.
When to use DRY
Reach for "DRY" when the conversation is specifically about don't repeat yourself. Principle that every piece of knowledge should have a single, unambiguous representation in a system. DRY done badly creates the wrong abstractions — duplication is cheaper than the wrong coupling.
When to use SOA
Reach for "SOA" when the conversation is specifically about service oriented architecture. Architectural style where business capabilities are exposed as loosely coupled, reusable services. SOA was the precursor to microservices — same idea, heavier ceremony.
FAQs
What is the difference between DRY and SOA?
DRY stands for Don't Repeat Yourself — Principle that every piece of knowledge should have a single, unambiguous representation in a system. DRY done badly creates the wrong abstractions — duplication is cheaper than the wrong coupling. SOA stands for Service Oriented Architecture — Architectural style where business capabilities are exposed as loosely coupled, reusable services. SOA was the precursor to microservices — same idea, heavier ceremony.
Are DRY and SOA the same thing?
No. They're often used in the same conversation because they're related, but they describe different concepts. DRY = Don't Repeat Yourself. SOA = Service Oriented Architecture.
When should I use DRY vs SOA?
Use DRY when you're specifically referring to don't repeat yourself. Use SOA when the topic is service oriented architecture.