Clean Architecture entity vs model

Clean Architecture is also layered architecture . The layer domain (entities) is in the center surrounded by the application layer (use cases). The outer layer consists of ports and adapters that adapt the application to external systems (web, DB, UI) via controllers, repositories, presenters.

Use Cases (a Clean Architecture term) are similar to Application Services in DDD. At least their relative positioning is. … Application Services. BookKnown asLayerDomain-Driven Design (DDD)Application ServiceApplicationClean Architecture (CA)Use CaseApplicationComparison of Domain-Driven Design and Clean Architecture … khalilstemmler.com › articles › domain-driven-design-vs-clean-architecture

The purpose of a use case is to serve a user’s use case of the system . For example, “turn light on” or “send email to tenant”. In code, the entry point of a Use Case is a class that has one public method.

The main purpose of Clean Architecture is to allow the business to adapt to changing technology and interfaces . While the internet might move from desktop to mobile, or from mobile to virtual assistant, the core business remains the same.