Query Attributes by H3 with DynamoDB

TL;DR
Use H3 cell IDs as partition keys in DynamoDB for fast attribute lookups. Resolve H3 on the server (Lambda) or on the client, then do a direct key-value read.

Description

Discrete Global Grid Systems allow...

A client requests attributes for a location. Client computes h3 → calls API Gateway with h3 → (optionally) direct DynamoDB HTTP API pass-through or a thin Lambda.

When to Use

• Low-latency point-in-cell lookups at web scale.
• You have denormalized attributes per H3 cell/resolution.
• Cost-predictable key-value access (no scans/joins).

Trade-offs

• H3 resolution choice impacts precision vs. storage.
• Updates require re-materializing affected cells.
• Hotspots possible (popular cells / zoomed-in areas) → consider caching or replication.
• Client-side H3 reduces server cost but exposes resolution logic to clients.

References

TODO.