liveBook · Manning

Serialization

Serialization is the coordination of potentially concurrent operations so that specified operations occur one at a time in a defined order.

How 2 Manning books explain it

Elixir in Action, Third Edition

Serialization is the handling of competing operations one at a time in a defined sequential order.

How it is used
Frames process-based state management and exposes the scalability cost of funneling many clients through one server.
How deep it goes
Shows message-loop implementation and a production bottleneck, but stops short of detailed ordering guarantees.
Examples
Uses a GenServer key-value store, benchmark results, and a TodoServer backed by a TodoList.
What you can do after
Build it from scratch with a receive loop that applies requests sequentially and carries forward updated state.

Read how Elixir in Action, Third Edition explains serialization →

C++ Concurrency in Action, Second Edition

Serialization is the restriction of concurrent operations so that they execute in a sequential order rather than simultaneously.

How it is used
Frames serialization as a design constraint when building lock-based concurrent data structures.
How deep it goes
Defines mutex-based serialization and gives design questions for reducing it, while deferring lock-free data structures.
What you can do after
Evaluate lock scope, mutex partitioning, and operation-level protection to reduce serialization while preserving operational semantics.

Read how C++ Concurrency in Action, Second Edition explains serialization →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.