การจัดการข้อกังวลที่ครอบคลุมหลายส่วน

In software development, cross-cutting concerns are aspects of a system that affect many parts of the application but are not part of its core business logic. Think of them as system-wide services.

• Logging: Recording events for debugging or auditing.
• Authentication: Verifying a user's identity.
• Authorization: Determining what an authenticated user can do.
• Caching: Storing frequently accessed data for faster retrieval.
• Transaction Management: Ensuring data consistency across multiple operations.

Clean Architecture emphasizes keeping your core business logic (Entities and Use Cases) independent of external frameworks and delivery mechanisms. This is enforced by the Dependency Rule: dependencies must only flow inwards.

The challenge arises because cross-cutting concerns often rely on specific external frameworks (e.g., a logging library, a security framework). How can we implement these concerns without violating the Dependency Rule and coupling our core logic to external details?

Let's take logging as an example. If a CreateUserUseCase directly calls a logging framework like Log4j or SLF4J, it creates a dependency on that specific framework.

CreateUserUseCase → Log4j

This violates the Dependency Rule because the inner layer (Use Case) would depend on an outer layer (Frameworks/Drivers). Our core logic should not care how logs are written, only that they need to be written.

To solve this, we introduce an interface in our inner (Use Case) layer. This interface, often called an Output Port, defines the contract for logging. The Use Case depends on this abstraction, not a concrete implementation.

The actual logging framework implementation lives in an outer layer (e.g., Infrastructure). This concrete class acts as an Adapter, implementing our ILogger port and delegating to the specific logging library.

Notice how ConsoleLogger depends on ILogger (an inner layer abstraction), respecting the Dependency Rule.

Now, our CreateUserUseCase can depend on the ILogger interface. The concrete ConsoleLogger is injected at runtime, typically by a Dependency Injection (DI) container, but we'll do it manually here for clarity.

Authentication (verifying who a user is) should occur at the application's entry points, not within the core Use Cases. The Use Case should only receive already authenticated user information.

• Middleware/Filters: In web applications, these intercept requests before they reach controllers.
• Input Port Decorators: You can wrap a Use Case with a decorator that handles authentication before delegating to the actual Use Case.

This ensures the Use Case remains focused on business logic, free from security framework details.

Authorization (what an authenticated user can do) is often more complex. While basic authorization can also be handled at the entry point, more granular checks might involve the Use Case.

• Authorization Policies: Define separate objects or services that encapsulate authorization rules.
• Interceptors/Aspects: Apply these policies around Use Case execution, checking permissions before the core logic runs.
• The Use Case might depend on an IAuthorizationService interface (another Port) to query specific permissions.

The overarching principle for handling cross-cutting concerns in Clean Architecture is the Dependency Inversion Principle (DIP).

• High-level modules (Use Cases) should not depend on low-level modules (frameworks).
• Both should depend on abstractions (interfaces).
• Abstractions are defined in the inner layers, and their concrete implementations reside in the outer layers, injected at runtime.

This keeps your core logic clean, testable, and independent of external technologies.

Consider a ProcessOrderUseCase that needs to log critical steps. Which approach aligns best with Clean Architecture's Dependency Rule?

We've explored strategies to handle cross-cutting concerns like logging, authentication, and authorization within Clean Architecture:

• Abstract Concerns: Define interfaces (Ports) in inner layers for concerns like logging.
• Implement Adapters: Provide concrete implementations of these interfaces in outer layers (Adapters).
• Boundary Handling: Use middleware, decorators, or interceptors at application boundaries for authentication and authorization.
• Dependency Inversion: This principle is crucial for ensuring your core business logic remains clean, independent, and free from external framework details.