---
title: "Discussion on \"What Is Serialization? A Descent Into Memory (and the Climb Back Out)\" | Hashnode"
description: "Discussion on \"What Is Serialization? A Descent Into Memory (and the Climb Back Out)\". Why can’t a program just send its memory? Learn serialization in C++ through the stack, heap, pointers, byte order and RFC 4253, with code you can run"
url: "https://hashnode.com/posts/what-is-serialization-a-descent-into-memory-and-the-climb-back-out/6aeecd37551c17a8d7214cff"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [What Is Serialization? A Descent Into Memory (and the Climb Back Out)](https://nrtnnaik.hashnode.dev/what-is-serialization-a-descent-into-memory-and-the-climb-back-out?utm_source=hashnode&utm_medium=feed)

Why can’t a program just send its memory? Learn serialization in C++ through the stack, heap, pointers, byte order and RFC 4253, with code you can run

4d ago · 14 min read · nrtnnaik.hashnode.dev  
Read the article

-   [#serialization](https://hashnode.com/tag/serialization)
-   [#cpp-guide](https://hashnode.com/tag/cpp-guide)
-   [#byte-order](https://hashnode.com/tag/byte-order)
-   [#endianness](https://hashnode.com/tag/endianness)
-   [#stack-and-heap](https://hashnode.com/tag/stack-and-heap)
-   [#networking](https://hashnode.com/tag/networking)
-   [#pcapplusplus](https://hashnode.com/tag/pcapplusplus)
-   [#open-source](https://hashnode.com/tag/open-source)
-   [#ssh](https://hashnode.com/tag/ssh)
-   [#rfc-4253](https://hashnode.com/tag/rfc-4253)

## Written by

[Nartan Naik](https://hashnode.com/@nrtnnaik)

@nrtnnaik

  
[View profile](https://hashnode.com/@nrtnnaik)

Software Engineer · Full-stack & AI · CSE student at NIE Mysuru · Building with React, Node.js, FastAPI and LLMs

Hi, I'm Nartan, a Software Engineer focused on full-stack and AI applications, in my final year of B.E. Computer Science at NIE Mysuru. I came to CSE from a diploma in Automobile Engineering, so I like knowing how systems really work. What I've built: • CreatorLens AI: curates Instagram creator profiles; a staging pipeline gets past Vercel's 10-second limit • Unpack: AI codebase documentation; a custom scanner cuts LLM input by 98% • CyberCube: AI threat detection and SOC platform with explainable alerts Stack: React, Node.js, FastAPI, Flutter, Python, JavaScript, C++, SQL, Firebase, MongoDB, Supabase, PostgreSQL, Docker, GitHub Actions. I write about real project problems: serverless limits, LLM context and cost, API security, and shipping ML into products. Open to Software Engineering internships in India. GitHub: github.com/NartanNaik LinkedIn: linkedin.com/in/nartan-naik-90499a359

## Responses 1

Markdown supported · ⌘↵ to post

[c-wind](https://hashnode.com/@c-wind)

[2d ago](https://hashnode.com/posts/what-is-serialization-a-descent-into-memory-and-the-climb-back-out/6aeecd37551c17a8d7214cff/comment/6af1c7a6f0e8e69e817f17fe)

The stack-walk framing makes the pointer/serialization boundary much easier to follow than starting with a wire format. The 32-bit/64-bit sizeof(Person) comparison is especially effective: it shows why sending object bytes is brittle before even getting to endianness. I’ll be interested in how the follow-up handles SSH framing and length fields.