Developer Tools/Distributed Systems
Dan Abramov·Oct 2, 2025·13 min readBy #The User as the Authority
Query OptimizationRedisSecurityMonitoringPrompt EngineeringDeveloper Tools
AI summary
This article explains the resolution process for at:// URIs, focusing on how identity is decoupled from hosting in the AT protocol. It details how the protocol uses DIDs to identify data creators independently of the server hosting the content and discusses strategies like resolution caches and event streaming for performance.
Key points
- AT protocol URIs use the data creator's DID as the authority, intentionally separating the identity of the content owner from the physical hosting server.
- Resolving an at:// URI involves resolving a DID document to find the hosting service and subsequently fetching the record from that service.
- For production-grade applications, using a resolution cache for DID lookups is recommended to avoid redundant network overhead.
- Event streaming (e.g., via Jetstream) allows applications to populate local databases with AT protocol data, reducing the need for on-demand URI resolution.