[go: up one dir, main page]
Scribd
Upload
11 views3 pages

Message Communication Models Distributed Systems

The document outlines the message communication model in distributed systems, highlighting four main types based on message lifetime and synchronization: Transient Synchronous, Transient Asynchronous, Persistent Synchronous, and Persistent Asynchronous. Each model has distinct characteristics regarding reliability and use cases, such as real-time services, gaming, online payments, and distributed applications. A comparison table summarizes the models, emphasizing their trade-offs between performance, reliability, and latency.

Uploaded by

pream.bagga23
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
11 views3 pages

Message Communication Models Distributed Systems

The document outlines the message communication model in distributed systems, highlighting four main types based on message lifetime and synchronization: Transient Synchronous, Transient Asynchronous, Persistent Synchronous, and Persistent Asynchronous. Each model has distinct characteristics regarding reliability and use cases, such as real-time services, gaming, online payments, and distributed applications. A comparison table summarizes the models, emphasizing their trade-offs between performance, reliability, and latency.

Uploaded by

pream.bagga23
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Message Communication Model in Distributed Systems

Introduction
In distributed systems, nodes or processes interact by exchanging messages over a network. The message
communication model defines how messages are sent, delivered, and acknowledged. Two primary dimensions of this
model are:
1. Message Lifetime: Transient vs Persistent
2. Synchronization: Synchronous vs Asynchronous
Combining these gives us four main types of communication models.

1. Transient Synchronous Communication


Message Lifetime: Transient
Delivery: Synchronous

- The sender sends a message and waits (blocks) until the receiver acknowledges it.
- If the receiver is not available or the system fails, the message is lost.
- This model is lightweight but unreliable.

Examples:
- Remote Procedure Calls (RPC)
- Direct client-server request-response communication

Use Cases:
- Real-time services requiring immediate feedback

2. Transient Asynchronous Communication


Message Lifetime: Transient
Delivery: Asynchronous

- The sender sends a message and continues execution without waiting for a response.
- If the receiver is unavailable, the message is lost.
- This is the fastest but least reliable model.

Examples:
- UDP datagrams
- Non-critical logging or telemetry

Use Cases:
Message Communication Model in Distributed Systems

- Gaming, live metrics, or system monitoring

3. Persistent Synchronous Communication


Message Lifetime: Persistent
Delivery: Synchronous

- Messages are stored in a buffer or queue until the receiver processes them.
- The sender waits for confirmation before continuing.
- Ensures reliability but increases latency.

Examples:
- Kafka with blocking APIs
- Durable messaging services with acknowledgments

Use Cases:
- Online payments, ticket booking systems

4. Persistent Asynchronous Communication


Message Lifetime: Persistent
Delivery: Asynchronous

- Messages are stored until successfully delivered.


- Sender continues execution immediately after sending.
- Offers high reliability and fault tolerance.

Examples:
- Kafka, RabbitMQ, Email
- Message brokers in microservices

Use Cases:
- Distributed applications, task scheduling, decoupled systems

Summary
Comparison Table:

| Model | Lifetime | Sync? | Reliability | Example |


|-----------------------------|------------|-------|-------------|----------------------------|
Message Communication Model in Distributed Systems

| Transient Synchronous | Transient | Yes | Low | RPC, client-server |


| Transient Asynchronous | Transient | No | Low | UDP, telemetry |
| Persistent Synchronous | Persistent | Yes | High | Kafka (blocking), payments |
| Persistent Asynchronous | Persistent | No | High | Kafka, RabbitMQ, Email |

Each model serves different needs based on the trade-offs between performance, reliability, and latency.

You might also like