Why Store UTC: The Principle and Pitfalls
IANA Timezone Database vs Localized CLDR Names
Converting Timestamps and Presenting Localized Timezone Names
Handling DST Transitions: Ambiguous and Nonexistent Local Times
APIs and Client Responsibilities for Reliable Timezone Conversion
Practical Application: Checklists, Code Recipes, and API Examples
Store every timestamp as a single canonical instant in UTC — that simple rule prevents a long tail of scheduling regressions, reporting skew, and customer-visible surprises. Mixing offsets, local wall-clock values, or localized names into your canonical data model moves complexity into every query, join, and aggregation.
Teams surface the same symptoms again and again: recurring jobs run at the wrong hour after a DST change, audit logs show impossible orderings, and calendar invites land at different local times for different recipients.…