Streaming Dua Arah dan Pengendalian Aliran
Pahami cara mengelola aliran data berkelanjutan ke dua arah dan menerapkan pengendalian aliran dasar.
Streaming Dua Arah dan Pengendalian Aliran adalah pelajaran WebSockets & Realtime Systems Programming 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 WebSockets & Realtime Systems Programming, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus WebSockets & Realtime Systems Programming mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Beyond Simple Messages
So far, we've mostly thought about WebSockets as a way to send discrete messages back and forth. But what if you need to transfer a continuous stream of data?
This is where bidirectional streaming comes in. It's about maintaining a steady, ongoing flow of data simultaneously in both directions, not just isolated messages.
Why Bidirectional Streaming Matters
Imagine scenarios like:
- Live Audio/Video: Sending and receiving real-time media streams.
- Large File Transfers: Uploading or downloading big files in chunks.
- Real-time Analytics: Continuous updates for dashboards with high data volume.
For these, a constant 'river' of data is more efficient than many small, separate 'droplets'.
The Challenge of Data Flow
What happens if one side sends data much faster than the other can process it? Think of a firehose pouring water into a small cup.
The receiver's temporary storage (called a buffer) will quickly fill up. This can lead to:
- Data loss
- System slowdowns
- Memory exhaustion
This is a critical problem for continuous data flow.
Introducing Flow Control
To prevent overwhelming a receiver, we use Flow Control. It's a mechanism that manages the rate of data transmission between a sender and a receiver.
Its main goal is to ensure the sender doesn't send data faster than the receiver can handle, making the communication smooth and reliable.
Key Flow Control Concepts
Flow control relies on a few core ideas:
- Buffering: Temporary storage for data that's been sent but not yet processed by the receiver.
- Backpressure: A signal from the receiver to the sender, indicating it needs to slow down or pause.
- Pause/Resume: Explicit commands or implicit behaviors to halt and restart data flow.
Think of it like a traffic light for your data stream.
WebSocket Buffering in Node.js
When you use ws.send(data) in Node.js, the ws library manages an internal buffer for outgoing messages.
The ws.send() method returns a boolean:
true: Data was sent immediately or buffered successfully.false: The internal buffer is full. You should pause sending new data.
You can also check ws.bufferedAmount, which tells you how many bytes are currently in the outgoing buffer.
const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 8080 });
wss.on('connection', ws => {
console.log('Client connected');
// Check buffer size before sending
const currentBuffer = ws.bufferedAmount;
console.log(`Current buffer size: ${currentBuffer} bytes`);
const ok = ws.send('Hello, streaming!');
if (!ok) {
console.log('Buffer full right away!');
} else {
console.log(`Message sent. New buffer size: ${ws.bufferedAmount} bytes`);
}
ws.on('message', message => {
console.log(`Received: ${message}`);
});
ws.on('close', () => console.log('Client disconnected'));
});
console.log('Server running on port 8080');Server-Side Backpressure (Part 1)
To implement flow control, your server needs to react when its outgoing buffer is full. If ws.send() returns false, you must stop sending data until the buffer clears.
This prevents the server from consuming too much memory or overloading the client's connection.
Here's the core idea of pausing:
const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 8080 });
wss.on('connection', ws => {
let messageCounter = 0;
let isPaused = false;
function sendLotsOfData() {
if (isPaused) return; // Don't send if paused
while (messageCounter < 1000) { // Send 1000 messages
const data = `Data chunk ${messageCounter++}`;
const ok = ws.send(data);
if (!ok) {
console.log('Buffer full! Pausing send...');
isPaused = true; // Set flag to pause
break; // Stop sending for now
}
}
if (messageCounter >= 1000) {
console.log('All data chunks sent!');
}
}
sendLotsOfData(); // Start sending
ws.on('message', msg => {}); // Placeholder
ws.on('close', () => {}); // Placeholder
});Server-Side Backpressure (Part 2)
When the buffer clears enough for more data, the ws library emits a 'drain' event. This is your cue to resume sending!
Combining ws.send()'s return value with the 'drain' event creates robust server-side flow control.
Try running this complete example. You'll see 'Buffer full!' and 'Buffer drained!' messages as flow control kicks in.
const WebSocket = require('ws');
const wss = new WebSocket.Server({ port: 8080 });
wss.on('connection', ws => {
console.log('Client connected. Starting data stream...');
let messageCounter = 0;
let isSending = false; // Flag to manage sending state
function streamData() {
if (isSending) return; // Already sending, wait for drain or completion
isSending = true;
while (messageCounter < 500) { // Simulate sending 500 messages
const data = `Stream chunk ${messageCounter++} from server.`;
const ok = ws.send(data);
if (!ok) {
console.log(`Buffer full (${ws.bufferedAmount} bytes), pausing send...`);
isSending = false; // Stop sending until drain
break; // Exit loop, wait for drain
}
}
if (messageCounter >= 500) {
console.log('Finished sending all stream chunks.');
isSending = false;
}
}
streamData(); // Start sending data after connection
ws.on('drain', () => {
console.log('Buffer drained, resuming send.');
streamData(); // Resume sending
});
ws.on('message', message => {
console.log(`Received from client: ${message}`);
// In a real app, client might also stream data here,
// requiring similar flow control logic on the client side.
});
ws.on('close', () => console.log('Client disconnected'));
ws.on('error', error => console.error('WebSocket error:', error));
});
console.log('WebSocket server started on port 8080. Connect a client to see streaming.');Client-Side Flow Control
While the server-side example focuses on outgoing data, clients also need to manage incoming streams and potentially their own outgoing streams.
On the client (browser JavaScript):
- For receiving data, you might buffer incoming messages if processing is slow.
- For sending large data (e.g., file uploads), you'd send in chunks and might need server-sent acknowledgments or explicit 'pause' signals to implement client-side backpressure.
The core principles remain the same: don't send faster than the receiver can handle.
Quick Check: Flow Control Logic
Consider a Node.js WebSocket server trying to send a large amount of data to a client. Which of the following statements about implementing server-side flow control are TRUE?
Recap: Mastering Realtime Streams
In this lesson, we explored bidirectional streaming and the crucial concept of flow control in WebSockets.
- Bidirectional streaming allows for continuous, simultaneous data flow, ideal for applications like live video or large data transfers.
- Flow control, using mechanisms like buffering, backpressure, and the
'drain'event, prevents overwhelming either the sender or receiver. - Implementing proper flow control is essential for building robust, high-performance, and reliable real-time applications.
Keep these principles in mind as you build your next streaming WebSocket application!
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Streaming Dua Arah dan Pengendalian Aliran” gratis?
Ya — teks lengkap “Streaming Dua Arah dan Pengendalian Aliran” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus WebSockets & Realtime Systems Programming, upgrade ke CoddyKit PRO. Kursus WebSockets & Realtime Systems Programming mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Streaming Dua Arah dan Pengendalian Aliran”?
Pahami cara mengelola aliran data berkelanjutan ke dua arah dan menerapkan pengendalian aliran dasar. Kamu berlatih WebSockets & Realtime Systems Programming 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 WebSockets & Realtime Systems Programming?
Tidak diperlukan pengalaman sebelumnya. WebSockets & Realtime Systems Programming 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 “Streaming Dua Arah dan Pengendalian Aliran” 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 WebSockets & Realtime Systems Programming ini?
Ya. Setiap pelajaran WebSockets & Realtime Systems Programming 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
- Mengimplementasikan Pesan Publikasi/Perlangganan
- Permintaan-Respons melalui WebSockets
- Streaming Dua Arah dan Pengendalian Aliran
- Backpressure dan Pengelompokan Pesan