Fingerprinting — Aquilia Documentation
Comprehensive guide and documentation for Fingerprinting in the Aquilia framework. View API reference, examples, and implementation patterns.
AQUILARY / FINGERPRINTING Registry Fingerprinting Aquilia uses content-addressable fingerprinting to verify application configuration state, detect hot-reload requirements, and guarantee reproducible production deployments. Deterministic SHA-256 Generation The FingerprintGenerator compiles a canonical dictionary representation of the application state, serializes it to sorted JSON, and computes a SHA-256 hash. To ensure reproducibility across local machines, Docker images, and cloud providers, it filters out environment variations: Included in Hash App manifest names and versions Dependency relationships between modules Route paths, parameters, and HTTP methods Config keys and schemas (structure only) Excluded from Hash Environment variable values Absolute path structures Build or compilation timestamps Active runtime container references Verifying Fingerprints from aquilia.aquilary import FingerprintGenerator # Compute the fingerprint of the live registry generator = FingerprintGenerator() fingerprint = generator.generate(app_contexts, config, mode) print(f"Active Fingerprint: ") # -> "8f9e1a2b3c4d5e6f..." # If deployment fingerprint differs from frozen disk configuration: # 1. Hot reload module registry # 2. Re-compile route endpoints Runtime Registry Subsystem Overview )
Go to Homepage