Document generation as code: from days of debugging to sub-2ms PDFs

Banks waiting days for trade confirmations and manufacturers debugging print failures over VPNs share a root cause: treating PDF generation as a GUI task, not a software problem. Crystal Reports and heavy runtimes like headless Chrome or LaTeX create fragile, slow, and unrepeatable pipelines.

A real-world side project swaps those out for a Rust library, the lean Typst typesetter, and serverless architecture. With template caching, render times fall below 2 ms. More importantly, content-addressable storage and manifest-based versioning make the whole document bundle auditable and reproducible—a game-changer for compliance.

The approach treats templates like packages: immutable, hashed, and referenceable. The trade-off: Typst's DSL is new and not WYSIWYG, and the 2 ms speed relies on incremental changes. Still, a million PDFs cost less than 50 cents, and debugging shrinks from hours to minutes because both template and data are versioned.

Engineering leaders should see this as a blueprint for turning document workflows into a proper software discipline. The lesson isn't just about speed—it's that applying modern build, cache, and versioning patterns to neglected subsystems can eliminate operational firefighting and deliver regulatory confidence.