Scribd
Upload
8 views1 page

DataTransfer Evolution Overview

The document outlines the evolution of data transfer formats, highlighting text, XML, JSON, and Protobuf, each with varying levels of readability and efficiency. It explains the transmission flow involving compression and decompression to optimize data transfer size and speed. Key takeaways emphasize the benefits of each format, with JSON being lightweight and Protobuf offering compact binary representation.

Uploaded by

jkprajwal41
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
8 views1 page

DataTransfer Evolution Overview

The document outlines the evolution of data transfer formats, highlighting text, XML, JSON, and Protobuf, each with varying levels of readability and efficiency. It explains the transmission flow involving compression and decompression to optimize data transfer size and speed. Key takeaways emphasize the benefits of each format, with JSON being lightweight and Protobuf offering compact binary representation.

Uploaded by

jkprajwal41
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

8/13/25, 7:02 PM DataTransfer-Evolution - Overview

DataTransfer-Evolution
Last updated by | Sathappa Subramaniam | Aug 13, 2025 at 7:01 PM GMT+4

Data Transfer – Format Evolution

1. Formats Overview
Over time, data transfer formats have evolved to balance readability, structure, and efficiency.

a. Text Format

List Item 1: 
"ProductName": "Phone", "Price": 5000, "CategoryId": 1
List Item 2:
"ProductName": "Watch", "Price": 6000, "CategoryId": 1

b. XML

<root> 
<Products>
<Product_1>
<ProductName type="Text">Phone</ProductName>
<Price type="integer">5000</Price>
<CategoryId>1</CategoryId>
</Product_1>
<Product_2>
<ProductName type="Text">Watch</ProductName>
<Price type="integer">6000</Price>
<CategoryId>1</CategoryId>
</Product_2>
</Products>
</root>

c. JSON

[ 
{ "ProductName": "Phone", "Price": 5000, "CategoryId": 1 },
{ "ProductName": "Watch", "Price": 6000, "CategoryId": 1 }
]

d. Protobuf (Conceptual Mapping)

[ 
{ "A": "Phone", "B": 5000, "C": 1 },
{ "A": "Watch", "B": 6000, "C": 1 }
]

Note: Protobuf is stored/transmitted as binary bytes ( AA BB CC DD EE ), not human-readable text.

2. Transmission Flow

[ Original Data (~1 KB) ] 


↓
Compression
↓
[ Smaller Size ]
↓
Transfer (HTTP/TCP)
↓
Decompression
↓
[ Original Data (~1 KB) ]

Sender Receiver

Transfer
Original Data ~1 KB Compression Smaller Size Decompression Original Data ~1 KB
HTTP/TCP/UDP/CoAP

Compression reduces size for faster transfer.

Decompression restores original data after receipt.

Common HTTP compression: gzip , br .

With TCP, compression is handled at the application layer.

3. Key Takeaways
Text/XML → Human-readable, verbose.

JSON → Lighter, widely used in APIs.

Protobuf → Compact binary, faster to serialize/deserialize.

Compression can be applied to any format before sending.

[Link] 1/1

You might also like