Clean Architecture（再讀整潔架構）是由軟體工程師 Robert C. Martin
提出的一種軟體架構設計原則，旨在協助開發人員建立可維護、可擴展和可測試的軟體系統。這個概念強調將軟體系統分解成多個疊層，每個疊層負責不同的功能，並確保這些疊層之間保持良好的分離。
Clean Architecture 的核心思想是：
-
分離關注點（Separation of
Concerns）：將系統分為多個層次，每個層次應該關注特定的功能或業務邏輯。這樣可以使不同層次之間的變更不會互相影響。
-
依賴反轉（Dependency
Inversion）：高層次的模組不應該依賴於低層次的細節，而是兩者都應該依賴於抽象。這鼓勵使用介面或抽象類來定義模組之間的交互，從而實現鬆散的耦合。
-
清晰的邊界：架構的各層之間有明確的邊界，不同層次的代碼不會混在一起。例如，業務邏輯、資料存取、使用者介面等應該分別位於不同的層次。
-
可測試性：因為模組之間的依賴是通過抽象進行的，所以可以更容易地進行單元測試，並且可以輕鬆地模擬模組的依賴。
Clean Architecture
通常由以下幾個主要層次組成（層次的名稱和功能可能會因不同的解釋而略有不同，以下只是一個常見的例子）：
- 實體層（Entities）：包含業務實體和相關的業務邏輯，是整個架構的核心。
- 用例層（Use Cases）：包含應用程序的用例和操作，協調不同的實體和操作。
-
介面適配層（Interface
Adapters）：處理用戶介面和外部服務，將外部數據轉換為內部模型，並將內部操作暴露給外部。
-
框架和工具層（Frameworks and
Tools）：包含框架、庫、工具等，用於支援其他層次的實現。
透過這些層次的組織和分離，Clean Architecture
旨在提供一個可維護、可測試、可擴展且容易理解的軟體架構，有助於團隊開發高質量的軟體產品。但值得注意的是，Clean
Architecture
並不是一種特定的架構模板，而是一種指導原則，實際的架構可能會因應項目需求和技術選擇而有所不同。
實際運用在開發上，優點是檔案結構明確，能夠將介面、邏輯、資料溝通、套件的程式碼分開，但是在開發過程會增加很多步驟，特別是檔案的引用，每個
UseCase or Module 都要使用很像模組化的方式載入對應的 class or
function，增加開發的時間，有的時候也會失去了外部套件所提供的便利性 (usecase
層級，無法直接使用外部套件)
Clean Architecture, introduced by software engineer Robert C. Martin, is a software architectural design principle aimed at helping developers build maintainable, scalable, and testable software systems. This concept emphasizes breaking down software systems into multiple layers, each responsible for different functionalities, and ensuring a good separation between these layers.
The core ideas of Clean Architecture are:
- Separation of Concerns: The system is divided into multiple layers, and each layer should focus on specific functionalities or business logic. This helps ensure that changes in one layer do not affect others.
- Dependency Inversion: High-level modules should not depend on low-level details. Instead, both should depend on abstractions. This promotes loose coupling through the use of interfaces or abstract classes to define interactions between modules.
- Clear Boundaries: There are clear boundaries between the layers of the architecture, and code from different layers is not mixed. For example, business logic, data access, and the user interface should be located in separate layers.
- Testability: Since modules depend on abstractions, it's easier to perform unit testing and mock module dependencies.
Clean Architecture typically consists of the following main layers (layer names and functionalities may vary slightly depending on interpretation, but this is a common example):
- Entities: Contains business entities and related business logic, forming the core of the architecture.
- Use Cases: Contains application use cases and operations, coordinating different entities and actions.
- Interface Adapters: Handles user interfaces and external services, converting external data to internal models and exposing internal operations to the outside.
- Frameworks and Tools: Includes frameworks, libraries, and tools used to support the implementation of other layers.
Through this layered organization and separation, Clean Architecture aims to provide a software architecture that is maintainable, testable, scalable, and easy to understand, helping teams develop high-quality software products. However, it's worth noting that Clean Architecture is not a specific architectural template but rather a set of guiding principles. The actual architecture may vary depending on project requirements and technology choices.
When applying Clean Architecture in development, the advantages include clear file structures and the ability to separate code for interfaces, logic, data communication, and packages. However, the development process can involve more steps, especially in terms of file referencing. Each UseCase or Module requires loading corresponding classes or functions in a modular way, which can increase development time and sometimes reduce the convenience offered by external packages (external packages cannot be directly used at the usecase level).
留言
張貼留言