Last time, I shared with you how sneaky I was on transaction handling. Today, the opposite: I’ll tell you how I fixed the issue when I tried to be too sneaky.

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

A developer shares how a sneaky Regex-based bigint auto-detection during JSON deserialization caused JavaScript event loop freezes in production. The fix involved dropping the global Regex reviver and replacing it with an explicit upcasting pattern — a function that converts stored types (strings) to application types (Date, bigint) only for declared fields. This same upcasting mechanism naturally extends to schema versioning: handling structural changes between document/event versions (V1 flat fields vs V2 nested objects) using upcast (read) and downcast (write) functions. The pattern is applied to both Pongo (document store) and Emmett (event store), enabling backward and forward compatibility without batch migrations.

Parse, Don't Guess

<p>If you are interested in this sort of thing for Ruby (real AST/PEG parsing instead of Regex guessing): <a href="https://github.com/kettle-rb/tree_haver" target="_blank" rel="noopener nofollow">https://github.com/kettle-rb/tree_haver</a></p>
