Henge
Henge is a Python package for building data storage and retrieval interfaces for arbitrary data. Henge is based on the idea of decomposable recursive unique identifiers (DRUIDs), which are hash-based unique identifiers for data derived from the data itself. For arbitrary data with any structure, Henge can mint unique DRUIDs to identify data, store the data in a key-value database of your choice, and provide lookup functions to retrieve the data in its original structure using its DRUID identifier.
Henge was intended as a building block for sequence collections, but is generic enough to use for any data type that needs content-derived identifiers with database lookup capability.
Install
pip install henge
Quick Start
Create a Henge object by providing a database and a data schema. The database can be a Python dict or backed by persistent storage. Data schemas are JSON-schema descriptions of data types, and can be hierarchical.
import henge
schemas = ["path/to/json_schema.yaml"]
h = henge.Henge(database={}, schemas=schemas)
Insert items into the henge. Upon insert, henge returns the DRUID (digest/checksum/unique identifier) for your object:
druid = h.insert({"name": "Pat", "age": 38}, item_type="person")
Retrieve the original object using the DRUID:
h.retrieve(druid)
# {'age': '38', 'name': 'Pat'}
Tutorial
For a comprehensive walkthrough covering basic types, arrays, nested objects, and advanced features, see the tutorial notebook.
What are DRUIDs?
DRUIDs are a special type of unique identifiers with two powerful properties:
-
Decomposable: Identifiers in henge automatically retrieve structured data (tuples, arrays, objects). The structure is defined by a JSON schema, so henge can be used as a back-end for arbitrary data types.
-
Recursive: Individual elements retrieved by henge can be tagged as recursive, meaning these attributes contain their own DRUIDs. Henge can recurse through these, allowing you to mint unique identifiers for arbitrary nested data structures.
A DRUID is ultimately the result of a digest operation (such as md5 or sha256) on some data. Because DRUIDs are computed deterministically from the item, they represent globally unique identifiers. If you insert the same item repeatedly, it will produce the same DRUID -- this is true across henges as long as they share a data schema.
Persisting Data
In-memory (default)
Use a Python dict as the database for testing or ephemeral use:
h = henge.Henge(database={}, schemas=schemas)
SQLite backend
For persistent storage with SQLite:
from sqlitedict import SqliteDict
mydict = SqliteDict('./my_db.sqlite', autocommit=True)
h = henge.Henge(mydict, schemas=schemas)
Requires: pip install sqlitedict
MongoDB backend
For production use with MongoDB:
- Start MongoDB with Docker:
docker run --network="host" mongo
For persistent storage, mount a volume to /data/db:
docker run -it --network="host" -v /path/to/data:/data/db mongo
- Connect henge to MongoDB:
import henge
h = henge.Henge(henge.connect_mongo(), schemas=schemas)
Requires: pip install pymongo mongodict
Metadata
Release files for henge 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| henge-0.3.0.tar.gz | 25.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| henge-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.1 kB
Release files / henge-0.3.0.tar.gz
| Download URL | henge-0.3.0.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
727071a7d4dd240a60361cb999cb7933243cceb6cc979db267557001f98b879f
|
|
BLAKE2b-256 checksum How to use checksums |
6a4796679d88d838daac1f25c5f1b63b3b2b9309cb1f4e28563ca70d157f3da6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 25, 2026.
Transparency logRelease files / henge-0.3.0-py3-none-any.whl
| Download URL | henge-0.3.0-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
736348d5df6f4ca475c929dcb97279a94eb4c0427cdd58e22415592573a6ebcd
|
|
BLAKE2b-256 checksum How to use checksums |
0da74d13acff9b51da56588e1c8eaf7054f3f21ed71ed466620d37d71d81e829
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 25, 2026.
Transparency log