---
title: "Discussion on \"Why Storing Future Events in UTC is a Database Trap\" | Hashnode"
description: "Discussion on \"Why Storing Future Events in UTC is a Database Trap\". Avoid scheduling bugs. Learn why storing future events in UTC is a trap and how to design a resilient database schema using local time and IANA zone IDs."
url: "https://hashnode.com/posts/why-storing-future-events-in-utc-is-a-trap/6ab94c401209c8528da2d07b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why Storing Future Events in UTC is a Database Trap](https://doogal.dev/why-storing-future-events-in-utc-is-a-trap?utm_source=hashnode&utm_medium=feed)

Avoid scheduling bugs. Learn why storing future events in UTC is a trap and how to design a resilient database schema using local time and IANA zone IDs.

Sep 27 · 6 min read · doogal.dev  
Read the article

-   [#database](https://hashnode.com/tag/database)
-   [#backend](https://hashnode.com/tag/backend)
-   [#softwareengineering](https://hashnode.com/tag/softwareengineering)
-   [#systemdesign](https://hashnode.com/tag/systemdesign)

## Written by

[Doogal Simpson](https://hashnode.com/@doogal)

@doogal

  
[View profile](https://hashnode.com/@doogal)

"hey doogal, what is .... ?"

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
