liveBook · Manning

Zero-copy

Zero-copy is a data-transfer technique that accesses or exchanges data in its existing memory representation without copying it into another buffer.

How 2 Manning books explain it

First-Party Data Activation

A data-access pattern in which applications use data in its existing location without creating additional copies.

How it is used
Connects composable marketing solutions to a data lakehouse so AI can combine customer-centric and channel-centric data.
How deep it goes
Defines zero-copy, then qualifies it with partial implementations and intentional architectural trade-offs.
Examples
Contrasts copying audience membership while retaining personalization fields with a mostly zero-copy system.
What you can do after
Evaluate composable marketing architectures for consistent data, lower costs, reduced security risks, and deliberate trade-offs.

Read how First-Party Data Activation explains zero-copy →

Architecting an Apache Iceberg Lakehouse

Zero-copy data exchange transfers data between compatible systems without copying the underlying in-memory representation.

How it is used
Connects federated data platforms with analytics tools while reducing serialization overhead and memory use.
How deep it goes
Explains the Arrow in-memory columnar mechanism and its performance effects, but does not detail memory-management or compatibility guarantees.
Examples
Uses large-dataset retrieval, partitioned query results, BI dashboards, and notebook connections as performance scenarios.
What you can do after
Apply it via Apache Arrow, Arrow Flight, or ADBC to exchange analytical data with lower serialization costs.

Read how Architecting an Apache Iceberg Lakehouse explains zero-copy →

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.