Port Masukan dan Keluaran
Pahami cara Port Masukan dan Keluaran (antarmuka) menetapkan batas komunikasi antara Kasus Penggunaan dan lapisan eksternal.
Port Masukan dan Keluaran adalah pelajaran Clean Architecture & Design Patterns in Practice gratis di CoddyKit. Ini adalah pelajaran 3 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 Input & Output Ports?
In Clean Architecture, "Ports" are crucial interfaces that define how different layers communicate. They act like contracts.
Think of them as the "sockets" of your application's core logic. They specify what goes in (Input) and what comes out (Output).
Defining Input Ports
An Input Port is an interface defined by the Use Case layer. It declares the methods that an external layer (like a UI controller) can call to interact with the Use Case.
- It's the "what you can do" contract for the Use Case.
- It ensures the Use Case doesn't know about the UI or external callers.
Input Port: User Login
Here's a simple Input Port for a user login feature. It defines the operations the Use Case expects.
public interface UserLoginInputPort {
void login(String username, String password);
}
public class UserLoginUseCase implements UserLoginInputPort {
@Override
public void login(String username, String password) {
// Business logic for login
System.out.println("Attempting login for: " + username);
if (username.equals("admin") && password.equals("pass")) {
System.out.println("Login successful!");
} else {
System.out.println("Login failed.");
}
}
public static void main(String[] args) {
UserLoginInputPort loginService = new UserLoginUseCase();
loginService.login("admin", "pass");
loginService.login("user", "123");
}
}Defining Output Ports
An Output Port is also an interface, defined by the Use Case layer. It declares the methods that the Use Case will call to deliver results or interact with external services (like a database or UI presenter).
- It's the "what I need to tell you" contract.
- It keeps the Use Case unaware of specific implementations (e.g., how results are displayed).
Output Port: Login Presenter
This Output Port defines how the login result should be presented or handled. The Use Case calls these methods, but doesn't know how they are implemented.
public interface UserLoginOutputPort {
void presentLoginSuccess(String username);
void presentLoginFailure(String message);
}
public class ConsolePresenter implements UserLoginOutputPort {
@Override
public void presentLoginSuccess(String username) {
System.out.println("Welcome, " + username + "!");
}
@Override
public void presentLoginFailure(String message) {
System.out.println("Error: " + message);
}
public static void main(String[] args) {
UserLoginOutputPort presenter = new ConsolePresenter();
presenter.presentLoginSuccess("Alice");
presenter.presentLoginFailure("Invalid credentials.");
}
}How Use Cases Use Ports
The Use Case (or Interactor) depends on these port interfaces. It takes an Input Port as its public method and receives an Output Port through its constructor or method parameters.
This means the Use Case only knows about abstractions, not concrete implementations.
Use Case Connecting Ports
Here, our UserLoginUseCase now uses both ports. Notice it doesn't know if it's talking to a web UI, a mobile app, or a console!
public interface UserLoginInputPort {
void login(String username, String password);
}
public interface UserLoginOutputPort {
void presentLoginSuccess(String username);
void presentLoginFailure(String message);
}
public class UserLoginUseCase implements UserLoginInputPort {
private final UserLoginOutputPort outputPort;
public UserLoginUseCase(UserLoginOutputPort outputPort) {
this.outputPort = outputPort;
}
@Override
public void login(String username, String password) {
if (username.equals("admin") && password.equals("pass")) {
outputPort.presentLoginSuccess(username);
} else {
outputPort.presentLoginFailure("Invalid credentials.");
}
}
public static void main(String[] args) {
// In real app, this would be wired by a framework
UserLoginOutputPort presenter = new ConsolePresenter(); // From Scene 5
UserLoginInputPort loginService = new UserLoginUseCase(presenter);
loginService.login("admin", "pass");
loginService.login("user", "wrong");
}
}
class ConsolePresenter implements UserLoginOutputPort {
@Override
public void presentLoginSuccess(String username) {
System.out.println("Welcome, " + username + "!");
}
@Override
public void presentLoginFailure(String message) {
System.out.println("Error: " + message);
}
}Ports and the Dependency Rule
The use of Ports perfectly adheres to the Dependency Rule. The Use Case layer (core business logic) depends on interfaces (the Ports).
The outer layers (like UI or databases) then implement these interfaces, providing the concrete details without the core knowing about them.
Why Use Ports?
Ports offer powerful advantages:
- Decoupling: The Use Case is isolated from UI, database, or external services.
- Testability: You can easily mock or stub these interfaces for robust unit testing of Use Cases.
- Flexibility: You can swap out implementations (e.g., change database) without touching core logic.
- Clarity: They clearly define the boundaries and interactions of your application's core.
Quick Check: Port Roles
Consider the roles of Input and Output Ports in Clean Architecture.
Recap: Ports as Boundaries
We learned that Input Ports are interfaces defining what a Use Case expects, acting as entry points.
Output Ports are interfaces defining what a Use Case delivers or needs from external services.
Together, they enforce the Dependency Rule, ensuring our core business logic remains independent, testable, and flexible.
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
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Port Masukan dan Keluaran” gratis?
Ya — teks lengkap “Port Masukan dan Keluaran” 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 “Port Masukan dan Keluaran”?
Pahami cara Port Masukan dan Keluaran (antarmuka) menetapkan batas komunikasi antara Kasus Penggunaan dan lapisan eksternal. 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 3 dari 4.
Berapa lama pelajaran “Port Masukan dan Keluaran” 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
- Merancang Entitas Bisnis
- Menerapkan Kasus Penggunaan (Interaktor)
- Port Masukan dan Keluaran
- Menegakkan Aturan Bisnis dengan Invarian