Turducken Architecture
ELI5 — The Vibe Check
Turducken architecture is when you have a system nested inside another system nested inside yet another system — like the famous chicken-inside-a-duck-inside-a-turkey dish. A React app inside an iframe inside a WordPress site inside a reverse proxy. Each layer adds complexity, latency, and confusion. Usually the result of 'we'll just wrap the old system' migration strategies that never complete.
Real Talk
Turducken architecture is an informal anti-pattern where multiple systems or frameworks are nested within each other, creating excessive indirection and complexity. It commonly occurs during incomplete migrations (new frontend wrapping old frontend wrapping legacy system) or when micro-frontends are composed without clear boundaries. Each layer adds overhead and potential failure modes.
When You'll Hear This
"The app is turducken architecture — a Vue SPA inside an iframe inside a Rails view." / "We need to finish the migration instead of adding another turducken layer."
Related Terms
Anti-Pattern
Anti-Pattern is the opposite of a design pattern — it's a commonly used approach that looks like it solves a problem but actually makes things worse.
Architecture
Architecture is the master blueprint for your app — like deciding whether to build a house, apartment block, or skyscraper before laying a single brick.
Legacy Code
Old code that nobody wants to touch but everyone depends on.
Micro Frontend
Micro frontends are microservices for the UI.
Over-engineering
Building a rocket ship when you just need a bicycle.