Pijine microservices komunikasi sareng sabaraha?

Question

Accepted Answer

Layanan komunikasi kanthi **synchronous** (request/response nganggo REST utawa gRPC) utawa **asynchronous** (pesen/events ngliwati broker sapertos Kafka utawa RabbitMQ).

## Synchronous (request/response)

Peng-unus ngantosan mbalèn. Prasaja lan intuitif, nanging panyambung katersediahan — yen sing dipanggil mosok, peng-unus kena pengaruh.

```http
GET /orders/42 HTTP/1.1
Host: orders-service
Accept: application/json
```

## Asynchronous (messaging/events)

Pang-kirim menerbitake pesen lan nerusake; konsumen ngrungokake mengko. Iki miscoupling layanan ing wektu.

```text
Order Service ──publish "OrderPlaced"──▶ [ Broker ] ──▶ Email Service
                                              │
                                              └──▶ Inventory Service
```

## Nalika nggunakake kaon

| Kabutuhan | Pilih |
|---|---|
| Swahe saketara kanggo pangguna | Synchronous |
| Miscoupling, buffering, fan-out | Asynchronous |
| Coupling temporal kuat OK | Synchronous |
| Resilience kanggo mosok downstream | Asynchronous |

## Jebakan

Dawa **chains synchronous** (A → B → C → D) kalikan latency lan kamungkinan kafoilan. Pilih async utawa agregasi yen bisa.

## Mengapa iku penting

Gaya komunikasi mbentuk ketahanan sistem: panggilan synchronous gampang dirembug nanging nggawe coupling runtime ketat, dene messaging asynchronous tuku miscoupling kanthi biaya consistency satrèngga.

Sistem nyata paling campur loro — sync kanggo wacan ngadhepi pangguna, async kanggo workflow latar mburi.

Kabutuhan	Pilih
Swahe saketara kanggo pangguna	Synchronous
Miscoupling, buffering, fan-out	Asynchronous
Coupling temporal kuat OK	Synchronous
Resilience kanggo mosok downstream	Asynchronous