Clean Architecture & Design Patterns in Practice · Pelajaran

Menangani Perhatian Lintas Lapisan

Terapkan strategi untuk pencatatan log, autentikasi, dan otorisasi tanpa melanggar Aturan Dependensi atau mengotori logika inti.

Pelajaran 1 dari 411 langkah

Menangani Perhatian Lintas Lapisan adalah pelajaran Clean Architecture & Design Patterns in Practice gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Clean Architecture & Design Patterns in Practice, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Clean Architecture & Design Patterns in Practice mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

What are Cross-Cutting Concerns?

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.

The Clean Architecture Dilemma

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?

Logging Without Pollution

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.

Defining a Logging Port

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.

package application.ports;

public interface ILogger {
    void info(String message);
    void error(String message, Throwable t);
}

Implementing the Logger Adapter

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.

package infrastructure.logging;

import application.ports.ILogger; // Depends on inner layer

public class ConsoleLogger implements ILogger {
    @Override
    public void info(String message) {
        System.out.println("[INFO] " + message);
    }

    @Override
    public void error(String message, Throwable t) {
        System.err.println("[ERROR] " + message + " - " + t.getMessage());
    }
}

Logger in a Use Case

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.

package application.usecases;

import application.ports.ILogger;
import infrastructure.logging.ConsoleLogger;

public class CreateUserUseCase {
    private final ILogger logger;

    public CreateUserUseCase(ILogger logger) {
        this.logger = logger;
    }

    public void execute(String username) {
        logger.info("Attempting to create user: " + username);
        // ... business logic to create user ...
        logger.info("User created successfully: " + username);
    }
}

public class Main {
    public static void main(String[] args) {
        // Manual Dependency Injection for demonstration
        ILogger consoleLogger = new ConsoleLogger();
        CreateUserUseCase useCase = new CreateUserUseCase(consoleLogger);
        useCase.execute("Alice");
    }
}

Handling Authentication

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 with Policies

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.

DI for Cross-Cutting Concerns

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.

Applying Clean Concerns

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

Jawab di pelajaran interaktif

Recap: Keeping Core Clean

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.

Gratis untuk memulai

Belajar Clean Architecture & Design Patterns in Practice dengan tutor AI — gratis

Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.

Kursus: 12
Pelajaran: 48

Mulai belajar gratis Lihat kursus lengkapnya

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Menangani Perhatian Lintas Lapisan” gratis?

Ya — teks lengkap “Menangani Perhatian Lintas Lapisan” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Clean Architecture & Design Patterns in Practice, upgrade ke CoddyKit PRO. Kursus Clean Architecture & Design Patterns in Practice mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Menangani Perhatian Lintas Lapisan”?

Terapkan strategi untuk pencatatan log, autentikasi, dan otorisasi tanpa melanggar Aturan Dependensi atau mengotori logika inti. Kamu berlatih Clean Architecture & Design Patterns in Practice dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Clean Architecture & Design Patterns in Practice?

Tidak diperlukan pengalaman sebelumnya. Clean Architecture & Design Patterns in Practice di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.

Berapa lama pelajaran “Menangani Perhatian Lintas Lapisan” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Clean Architecture & Design Patterns in Practice ini?

Ya. Setiap pelajaran Clean Architecture & Design Patterns in Practice menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

← Kembali ke Clean Architecture & Design Patterns in Practice