LogoLogo
HomeGitHub RepoBook Demo
version-3.5.x
version-3.5.x
  • Introduction
  • Installation
  • Quick start
  • Mental model
  • Architecture
  • Walkthrough
    • Editing a Package
    • Uploading a Package
    • Installing a Package
    • Getting Data from a Package
    • Working with the Catalog
    • Working with a Bucket
  • API Reference
    • quilt3
    • quilt3.Package
    • quilt3.Bucket
    • CLI, environment
    • Known limitations
  • Catalog
    • Configuration
    • Preview
    • Search & query
    • Metadata for teams
    • Admin UI
    • Embed
  • Advanced Usage
    • Filtering a Package
    • .quiltignore
    • Materialization
    • Working with Manifests
    • S3 Select
    • Workflows
    • Enterprise install
    • S3 Events, EventBridge
  • More
    • Frequently Asked Questions
    • Troubleshooting
    • Contributing
    • Changelog
Powered by GitBook
On this page

Was this helpful?

Architecture

PreviousMental modelNextEditing a Package

Last updated 3 years ago

Was this helpful?

Quilt data packages are reproducible, discoverable, and trusted data sets that live in blob storage.

A package manifest includes both metadata and physical keys to primary data.

All package metadata and data are stored in your S3 buckets. A slice of the package-level metadata, as well as S3 object contents, are sent to an ElasticSearch cluster managed by Quilt. All Quilt package manifests are accessible via SQL using AWS Athena.