Object store
An object store is a storage system that persists and retrieves discrete data objects by identifiers or keys, often with associated metadata.
Architecting an Apache Iceberg Lakehouse
Object storage is a storage system that manages data as self-contained objects addressed through a service interface rather than a hierarchical filesystem.
- How it is used
- Anchors the lakehouse storage layer by providing scalable, durable, API-accessible storage for analytical data and metadata.
- How deep it goes
- Explains object structure, flat namespaces, metadata, distribution, and storage-compute tradeoffs, while stopping short of vendor-specific implementation detail.
- Examples
- Uses Amazon S3, MinIO, path-shaped keys, Parquet files, and a hybrid regulated-bank architecture as concrete examples.
- What you can do after
- Evaluate object-storage options against scalability, latency, resilience, cost, compliance, and S3-compatible lakehouse integration requirements.
Read how Architecting an Apache Iceberg Lakehouse explains object store →
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
An object store is a storage system that manages data as objects identified by keys rather than as files in a hierarchical filesystem.
- How it is used
- Stores backups, static website content, and application uploads without keeping those objects on application servers.
- How deep it goes
- Defines object components and buckets, then works through CLI website setup and SDK image access; distributed-store internals are not detailed here.
- Examples
- Uses a static HTML website, an image gallery, and access-log processing to show storing and retrieving objects.
- What you can do after
- Operate/configure Amazon S3 buckets for object uploads and static hosting, while checking public access and usage-based costs.
HTML5 in Action
An object store is an IndexedDB database structure that stores a collection of objects under keys.
- How it is used
- Stores task objects locally for a mobile application's task-management features.
- How deep it goes
- Explains store creation, indexed searching, updates, and deletion through application steps rather than database internals.
- Examples
- Uses a task-list app to search descriptions, mark tasks complete, and delete tasks.
- What you can do after
- Apply it via IndexedDB to create a store, search its objects, and update or delete them.
Machine Learning Platform Engineering
An object store is a storage system that manages data as objects identified by keys, typically including their content and metadata.
- How it is used
- Stores prepared ML datasets outside the workstation so pipelines can access them and MLflow can track their paths.
- How deep it goes
- Walks through bucket creation, client configuration, uploads, and dataset-path logging; leaves object-store internals unexplained.
- Examples
- Uses run-specific training, test, and reference CSVs plus uploaded object-detection images and labels.
- What you can do after
- Operate/configure MinIO buckets and boto3 uploads, then record stored dataset paths in MLflow runs.
Read how Machine Learning Platform Engineering explains object store →
Data Pipelines with Apache Airflow, Second Edition
Object Storage is an Airflow feature that provides a unified syntax for interacting with object-storage systems and transferring data between them.
- How it is used
- Stages data for transfers and processing between Airflow tasks, databases, containers, and AWS services.
- How deep it goes
- Works through S3 copying and hook-based transformation, but does not demonstrate a storage-independent object-store API.
- Examples
- Uses an Airbnb listings pipeline with MinIO and an MNIST pipeline that converts S3 data for SageMaker.
- What you can do after
- Apply it via S3Hook and S3CopyObjectOperator to prepare stored data, then verify individual tasks with `airflow tasks test`.
Read how Data Pipelines with Apache Airflow, Second Edition explains object store →
LLMs in Production
An object storage system stores data as independently addressable objects distributed across storage infrastructure.
- How it is used
- Uses object storage to hold large LLM assets reliably before service startup and model loading.
- How deep it goes
- Explains fragmentation, federation, replication, availability, and retrieval costs, then stops short of detailed storage implementation.
- Examples
- Uses GCS, S3, cloud buckets, compiled LLMs, and fused buckets as concrete storage and retrieval examples.
- What you can do after
- Evaluate storage choices for large model assets while accounting for reliability, retrieval speed, and boot-time loading.
Grokking Software Architecture
An object store is a persistent storage system that manages data as individually addressable objects with associated metadata.
- How it is used
- Moves uploaded data off disposable application servers into persistent external storage.
- How deep it goes
- Contrasts local and S3 upload code, without detailing object-store internals.
- Examples
- Uses Python and boto3 to upload profile.jpg to an S3 bucket instead of saving it locally.
- What you can do after
- Apply it via boto3 to store uploads outside the application server.
Read how Grokking Software Architecture explains object store →
Also covered in
- Digital Twins in Action
- Kubernetes for Developers
- Kafka for Architects
- Vanilla WebIn early access (MEAP)
- Machine Learning System Design
- Cloud Observability in Action
- Build Python Web Apps with Streamlit
- Apache Kafka in Action
What to know first
- HTMLHTML is the standard markup language for structuring content and elements in documents on the web.
- JavaScriptJavaScript is a high-level, dynamically typed programming language standardized as ECMAScript and used for web and general-purpose programming.
- JSONJSON is a language-independent text-based data-interchange format that represents structured values using objects, arrays, strings, numbers, booleans, and null.
- NoSQL databaseA NoSQL database is a database system organized primarily around nonrelational data models rather than the traditional relational table model.
Related concepts
- static siteused by · A static site is a website primarily devoted to presenting content through fixed or prebuilt pages rather than pages dynamically generated for each request.
- database indexhas part · A database index is an auxiliary data structure that organizes keys or references to records to support efficient lookup and retrieval.
- IndexedDBpart of · IndexedDB is a browser API for asynchronously storing and querying structured data in transactional, indexed client-side databases.
- Objectuses · java.lang.Object is the root class of Java’s reference-type hierarchy and defines methods inherited by Java reference types.
Questions about object store
What is object store?
An object store is a storage system that persists and retrieves discrete data objects by identifiers or keys, often with associated metadata.
Which Manning books explain object store?
Architecting an Apache Iceberg Lakehouse, Amazon Web Services in Action, Third Edition: An in-depth guide to AWS, HTML5 in Action, Machine Learning Platform Engineering, Data Pipelines with Apache Airflow, Second Edition, LLMs in Production and Grokking Software Architecture.
What should I know before learning object store?
Manning books that teach object store usually introduce HTML, JavaScript, JSON and NoSQL database first.
What is object store part of?
Object store is part of IndexedDB. IndexedDB is a browser API for asynchronously storing and querying structured data in transactional, indexed client-side databases.
What are the parts of object store?
Object store includes database index.
What is object store also called?
Object store is also called object storage.
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.






