Sequelize timezone option vs application-level UTC conversion in a moleculer-db service

Answer to the Core Question

Using sequelize with timezone: '+00:00' is sufficient to guarantee that every broker node writes the same UTC value to the database, regardless of the node’s local time zone. The conversion is performed by Sequelize before the query is sent to the driver, so the driver’s session time zone or the database’s own conversion logic does not introduce divergence.

When the timezone option is omitted, Sequelize falls back to the Node process’s local time zone. In a heterogeneous cluster this means that two nodes with different TZ settings could serialize the same JavaScript Date into different UTC strings, resulting in inconsistent stored values. In that scenario, normalizing dates to UTC in application code is the safer approach.

Confirmed Facts

• Sequelize 6+ applies the timezone setting to all Date values before they reach the database driver.
• MySQL TIMESTAMP and PostgreSQL TIMESTAMPTZ store UTC internally; the database does not alter the value once it is sent.
• If a non‑timezone‑aware column (e.g., MySQL DATETIME) is used, Sequelize’s timezone conversion may not be applied consistently.
• Driver‑level conversion only matters when the driver is the one interpreting the string; with timezone set, the driver receives a UTC string and simply stores it.

Practical Verification Steps

1. Set up a test database. Create a table with a TIMESTAMP (MySQL) or TIMESTAMPTZ (PostgreSQL) column.
2. Write a known UTC date.

   const utcDate = new Date('2026-10-11T09:03:12Z');
   await Model.create({ createdAt: utcDate });
   

3. Read the raw value. Use a raw query to retrieve the stored string and compare it to the original UTC string.

   const result = await sequelize.query('SELECT created_at FROM table LIMIT 1', { type: sequelize.QueryTypes.SELECT });
   console.log(result[0].created_at); // Should output 2026-10-11 09:03:12
   

4. Repeat across nodes with different TZ settings. Launch two Node processes, one with TZ=America/New_York and another with TZ=Asia/Tokyo, both pointing to the same database. Perform the same write and read test.
5. Compare the stored values. With timezone: '+00:00' they must match; without it they will differ.
6. Automate with Moleculer test utilities. Spin up two broker instances in the test environment, each with a distinct process.env.TZ, perform the write, then query the shared database to assert equality.

Missing Diagnostic Detail

To fine‑tune the recommendation, could you confirm the column type you plan to use for timestamps (e.g., TIMESTAMP vs DATETIME) and the database driver versions (mysql2, pg)? These details affect how Sequelize’s timezone option interacts with the underlying DB.