Clean Architecture
Clean Architecture is a software architecture concept proposed by Robert C. Martin that organizes code into concentric layers where dependencies point exclusively inward, ensuring that business logic remains independent of specific UI frameworks or database implementations. This separation allows core domain logic to be developed and tested without coupling to external infrastructure concerns.
Timeline (last 90 days)
DSupport adopts Clean Architecture and Ports & Adapters; its modules include contract, core, adapters, mcp-orders, mcp-tickets, cli, server, app, and eval, with dependencies pointing only inward.
Clean Architecture, proposed by Robert C. Martin, emphasizes that the direction of dependencies should always point toward the inner business rules.
Clean Architecture, proposed by Robert C. Martin, emphasizes the dependency rule—outer layers may depend on inner layers, but inner layers must not depend on outer layers.
Clean Architecture in Android is typically implemented as a three-layer structure consisting of the presentation layer, domain layer, and data layer, with the Repository pattern implementing dependency inversion.
In modern Android architectures (such as MVVM, MVI, or Clean Architecture), the data layer is the sole channel through which the application interacts with external data sources, responsible for data retrieval, transformation, and persistence.
Encapsulating complex game rules in a UI-agnostic core engine—making the game engine exist as an independent class library that does not reference UI namespaces—enables dependency inversion and facilitates future migration to frontends such as WPF, Avalonia, MAUI, or Unity without modifying game logic.
All Facts (8)
整洁架构（Clean Architecture）由Robert C. Martin（Uncle Bob）提出
95%UnverifiedClean Architecture is a software architecture concept proposed by Robert C. Martin, whose core idea is to divide code into multiple concentric circle layers where dependencies can only point inward from the outside.
60%UnverifiedDSupport adopts Clean Architecture and Ports & Adapters; its modules include contract, core, adapters, mcp-orders, mcp-tickets, cli, server, app, and eval, with dependencies pointing only inward.
50%UnverifiedClean Architecture, proposed by Robert C. Martin, emphasizes that the direction of dependencies should always point toward the inner business rules.
50%UnverifiedClean Architecture, proposed by Robert C. Martin, emphasizes the dependency rule—outer layers may depend on inner layers, but inner layers must not depend on outer layers.
50%UnverifiedClean Architecture in Android is typically implemented as a three-layer structure consisting of the presentation layer, domain layer, and data layer, with the Repository pattern implementing dependency inversion.
50%UnverifiedIn modern Android architectures (such as MVVM, MVI, or Clean Architecture), the data layer is the sole channel through which the application interacts with external data sources, responsible for data retrieval, transformation, and persistence.
50%UnverifiedEncapsulating complex game rules in a UI-agnostic core engine—making the game engine exist as an independent class library that does not reference UI namespaces—enables dependency inversion and facilitates future migration to frontends such as WPF, Avalonia, MAUI, or Unity without modifying game logic.
50%