# Separation of Concerns

*phrase*

say it: **“sep-uh-RAY-shun uv kun-SURNZ”** **/ˌsɛpəˈreɪʃən əv kənˈsɝnz/**

Keeping each job a program does, such as its data, its rules, its drawing and its requests, in a place of its own.

## What is **separation of concerns**?

**Separation of concerns** means keeping each job a program does in its own place, so a change to one job doesn't touch the others. MVC separates the data and rules from the drawing and from handling requests; middleware separates the checks every request needs from each endpoint's own work.

## In a sentence

- “Thanks to **separation of concerns**, changing the page's colors never touched the late-fee rule.”

Level: Apprentice · [More OOP terms at this level](https://www.ask-codey.com/glossary?category=oop&level=2)

Updated: November 9, 2026

Source: https://www.ask-codey.com/glossary/separation-of-concerns
