Explain the concept of 'Screaming Architecture'.

Updated Apr 28, 2026

Short answer

The file structure should 'scream' what the application does, not what frameworks it uses.

Deep explanation

When you look at the top-level directory of a project, you should see folders like 'Orders', 'Payments', or 'Inventory' rather than 'Controllers', 'Models', and 'Views'. This makes the intent of the system obvious at a glance.

Real-world example

A project structure where you find 'PlaceOrder.ts' easily without digging through a generic 'services' folder.

Common mistakes

  • Organizing files by file type (e.g., all interfaces in one global folder).

Follow-up questions

  • How does this relate to Package by Feature?

More Clean Architecture interview questions

View all →