Explain how streaming works at a basic level and how TCP/IP fits in.
For the SQL portion, use the supplied stream and transport-event data to represent the relationship between an application stream and its TCP/IP delivery metrics.
stream_id, stream_name, transport_protocol, total_bytes, packet_count, retransmissions, avg_rtt_ms, and delivery_status.delivery_status is healthy when bytes were delivered with no retransmissions, degraded when retransmissions occurred, and no_data when no TCP bytes were recorded.stream_id ascending.| Column | Type | Description |
|---|---|---|
| stream_idPK | INT | Unique streaming session identifier |
| stream_name | VARCHAR(100) | Human-readable stream name |
| transport_protocol | VARCHAR(10) | Transport protocol expected by the stream |
| started_at | TIMESTAMP | Stream start time |
| Column | Type | Description |
|---|---|---|
| event_idPK | INT | Unique transport event identifier |
| stream_id | INT | Referenced streaming session |
| transport_protocol | VARCHAR(10) | Protocol observed for the event |
| event_type | VARCHAR(30) | Observed transport event type |
| bytes_transferred | INT | Bytes transferred in the event |
| retransmissions | INT | Number of retransmitted packets |
| rtt_ms | DECIMAL(8,2) | Round-trip time in milliseconds |
| event_at | TIMESTAMP | Event timestamp |