Pemutus Sirkuit dan Sekat
Pelajari cara menggabungkan pemutus sirkuit dengan pola sekat untuk mengisolasi kegagalan sumber daya dan mencegah masalah berantai.
Pemutus Sirkuit dan Sekat adalah pelajaran Microservices Communication Patterns (Saga, Circuit Breaker) 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 Microservices Communication Patterns (Saga, Circuit Breaker), dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Microservices Communication Patterns (Saga, Circuit Breaker) mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Patterns Work Better Together
Resilience patterns like Circuit Breaker and Bulkhead are powerful on their own. But in complex microservices, combining them offers even stronger protection.
Think of it like different layers of security for your application. Each layer catches different types of threats, creating a more robust defense.
Circuit Breaker Refresher
Remember the Circuit Breaker pattern? It's like an electrical circuit for your service calls.
- It monitors calls to a service.
- If failures exceed a threshold, it 'opens' the circuit.
- Once open, further calls fail immediately, preventing overload to the failing service and saving resources.
- After a timeout, it 'half-opens' to test if the service has recovered.
Bulkhead Pattern Refresher
The Bulkhead pattern isolates resources. Imagine a ship with watertight compartments (bulkheads).
- If one compartment floods, the others remain safe.
- In microservices, this means separating resource pools (e.g., thread pools, connections) for different services.
- A failure in one service's resource pool won't exhaust resources needed by other services.
Synergy: CB + Bulkhead
Why use both? They tackle different problems but complement each other perfectly.
- Circuit Breaker: Focuses on stopping requests to a failing service.
- Bulkhead: Focuses on isolating resources to prevent cascading failures due to resource exhaustion.
Together, they provide a comprehensive defense against various failure modes.
Bulkhead Helps Circuit Breaker
How does Bulkhead make Circuit Breaker better?
A Circuit Breaker needs to detect failures. If a service is overwhelmed (e.g., due to resource exhaustion) and all calls to it start failing slowly, it can take time for the Circuit Breaker to open.
By isolating resources, Bulkhead ensures that only a limited set of resources is consumed by a misbehaving service, preventing total exhaustion and allowing the Circuit Breaker to react more quickly and cleanly to actual service failures, rather than just resource starvation.
Circuit Breaker Helps Bulkhead
And how does Circuit Breaker enhance Bulkhead?
If a service is known to be failing (Circuit Breaker is OPEN), the Circuit Breaker will intercept requests and fail them immediately, before they even try to acquire a resource from the Bulkhead's pool.
This means the Bulkhead's limited resources are not wasted on calls destined to fail anyway, preserving them for other, potentially healthy, operations or for when the service recovers.
Real-World: Thread Pools
A common way to implement the Bulkhead pattern is using thread pools.
- Assign a dedicated, limited thread pool to calls for a specific external service.
- If that service is slow or unresponsive, only its dedicated threads get tied up.
- Other services, with their own thread pools, remain unaffected.
When combined with a Circuit Breaker, the CB stops calls before they even enter the thread pool if the service is down.
Code: CB & BH in Action
This example shows how a Circuit Breaker (CB) check happens before a Bulkhead (BH) resource acquisition. If the CB is open, the call fails immediately, saving BH resources.
import java.util.concurrent.Semaphore;
import java.util.concurrent.atomic.AtomicBoolean;
public class Main {
private static AtomicBoolean circuitOpen = new AtomicBoolean(false);
private static long lastFailureTime = 0;
private static final long RESET_TIMEOUT_MS = 5000;
private static final Semaphore serviceBulkhead = new Semaphore(2);
public static void callProtectedService(String callerId) {
// 1. Circuit Breaker check (Fail Fast)
if (circuitOpen.get()) {
if (System.currentTimeMillis() - lastFailureTime > RESET_TIMEOUT_MS) {
System.out.println(callerId + ": Circuit Half-Open. Testing service...");
circuitOpen.set(false); // Simple reset for demo
} else {
System.out.println(callerId + ": CB OPEN. REJECTED!");
return;
}
}
// 2. Bulkhead check (Resource Isolation)
boolean acquiredBulkhead = false;
try {
if (serviceBulkhead.tryAcquire()) {
acquiredBulkhead = true;
System.out.println(callerId + ": BH slot ACQUIRED. Calling...");
Thread.sleep(200); // Simulate work
if (callerId.equals("Call-3") || callerId.equals("Call-4")) {
System.out.println(callerId + ": Simulating FAILURE!");
circuitOpen.set(true);
lastFailureTime = System.currentTimeMillis();
} else {
System.out.println(callerId + ": Call SUCCESS.");
}
} else {
System.out.println(callerId + ": BH FULL. REJECTED!");
}
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
System.out.println(callerId + ": Call interrupted.");
} finally {
if (acquiredBulkhead) {
serviceBulkhead.release();
}
}
}
public static void main(String[] args) throws InterruptedException {
System.out.println("--- First calls (CB CLOSED) ---");
for (int i = 1; i <= 5; i++) {
final int callNum = i;
new Thread(() -> callProtectedService("Call-" + callNum)).start();
Thread.sleep(50);
}
Thread.sleep(1500);
System.out.println("\n--- Second calls (CB potentially OPEN) ---");
for (int i = 6; i <= 10; i++) {
final int callNum = i;
new Thread(() -> callProtectedService("Call-" + callNum)).start();
Thread.sleep(50);
}
Thread.sleep(6000);
System.out.println("\n--- Third calls (after reset) ---");
for (int i = 11; i <= 13; i++) {
final int callNum = i;
new Thread(() -> callProtectedService("Call-" + callNum)).start();
Thread.sleep(50);
}
}
}Combined Benefits
Using Circuit Breaker and Bulkhead together provides:
- Enhanced Fault Isolation: Prevents a single failing service from taking down others, both by stopping calls and by limiting resource usage.
- Improved Resource Management: Efficiently uses available resources, rejecting calls early if a service is known to be unhealthy.
- Faster Recovery: Allows healthy parts of the system to continue functioning, aiding overall system stability and recovery.
- Predictable Behavior: Helps maintain predictable response times and throughput under stress.
Quick Check
Which of the following statements accurately describe the benefits of combining the Circuit Breaker and Bulkhead patterns?
Recap: Stronger Together
In this lesson, we explored the powerful combination of the Circuit Breaker and Bulkhead patterns.
- We saw how Circuit Breaker prevents calls to failing services.
- We revisited how Bulkhead isolates resources.
- Most importantly, we learned how they mutually enhance each other to create a more resilient and stable microservices architecture.
Next, we'll see how Circuit Breakers can be combined with Retry Logic for even more robust error handling!
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pemutus Sirkuit dan Sekat” gratis?
Ya — teks lengkap “Pemutus Sirkuit dan Sekat” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Microservices Communication Patterns (Saga, Circuit Breaker), upgrade ke CoddyKit PRO. Kursus Microservices Communication Patterns (Saga, Circuit Breaker) mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Pemutus Sirkuit dan Sekat”?
Pelajari cara menggabungkan pemutus sirkuit dengan pola sekat untuk mengisolasi kegagalan sumber daya dan mencegah masalah berantai. Kamu berlatih Microservices Communication Patterns (Saga, Circuit Breaker) 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 Microservices Communication Patterns (Saga, Circuit Breaker)?
Tidak diperlukan pengalaman sebelumnya. Microservices Communication Patterns (Saga, Circuit Breaker) 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 “Pemutus Sirkuit dan Sekat” 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 Microservices Communication Patterns (Saga, Circuit Breaker) ini?
Ya. Setiap pelajaran Microservices Communication Patterns (Saga, Circuit Breaker) 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
- Pemutus Sirkuit dan Sekat
- Pemutus Sirkuit dengan Logika Percobaan Ulang
- Mengintegrasikan Pembatasan Laju
- Urutan Dekorator Ketahanan