Clean Architecture

A software design pattern that decouples business logic from frameworks and UI through strict concentric layers and dependency inversion.

Clean Architecture (popularized by Robert C. Martin in 2012) organizes code into four distinct layers: Entities, Use Cases, Interface Adapters, and Frameworks. By enforcing the Dependency Rule (source code dependencies only point inward) developers isolate the core domain from external volatility. This structure ensures that your business rules remain testable without a database, web server, or UI. It is the industry standard for building long-lived systems where the underlying technology stack (like SQL or React) can be swapped without rewriting the central logic.

https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html