Or how to make tradeoffs based on my Cloudflare D1 support

Architecture Weekly's publication is a central hub for architecture enthusiasts, offering insights into architectural design, urban planning, and sustainable architecture practices. Through articles, case studies, and architectural critiques, Architecture Weekly offers insights into iconic buildings, architectural trends, and innovative design solutions. Readers can learn about architectural history, design principles, and environmental sustainability initiatives to gain a deeper understanding of the built environment and its impact on society. Additionally, Architecture Weekly provides updates on the latest architectural projects, design competitions, and industry events to help architects and designers stay informed and inspired.

Architecture Weekly

Building a multi-database driver library (Dumbo) for Node.js revealed tradeoffs when supporting Cloudflare D1, which exposes databases via HTTP API and doesn't support traditional transactions. The solution uses D1's session-based repeatable reads and SQL batches to mimic transaction behavior, requiring explicit opt-in and accepting limitations like inability to rollback across multiple statements. This approach prioritizes API safety by making users acknowledge non-standard behavior while enabling practical use cases in event sourcing and document operations.

How I cheated on transactions