Meteor DDP serialization and timezone offset persistence in MongoDB

Meteor serializes JavaScript Date objects via the Distributed Data Protocol (DDP) as ISO 8601 UTC strings. While this ensures the point in time is preserved as an instant, the original regional timezone offset is stripped during the transport between the client and server.

MongoDB stores these values as UTC milliseconds since the epoch. Because Meteor does not provide a native schema-level mechanism to persist the originating timezone offset alongside the timestamp, any retrieved Date object is interpreted based on the local runtime environment of the machine where the code is executing.

This creates a challenge for applications that must maintain consistent temporal logic across different geographic regions, such as scheduling tools or localized logging, regardless of the user's local clock settings or the server's system time.

What is the most effective architectural pattern for storing and retrieving regional offsets in Meteor to ensure server-side calculation consistency? Should the offset be stored as a separate field in the collection, or handled via client-side transformation logic?