---
title: "Discussion on \"Part 6: Microtasks and Why Two Queues\" | Hashnode"
description: "Discussion on \"Part 6: Microtasks and Why Two Queues\". Why two queues, not one? The answer involves Promise chain atomicity, drain-to-completion, and an engineering trade-off the spec made in 2015."
url: "https://hashnode.com/posts/event-loop-microtasks-and-why-two-queues/6a52253510439b83c9e9daf0"
---

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

Discussion

# [Part 6: Microtasks and Why Two Queues](https://srekaravarshan.hashnode.dev/event-loop-microtasks-and-why-two-queues?utm_source=hashnode&utm_medium=feed)

Why two queues, not one? The answer involves Promise chain atomicity, drain-to-completion, and an engineering trade-off the spec made in 2015.

Jul 11 · 28 min read · srekaravarshan.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#promises](https://hashnode.com/tag/promises)
-   [#microtasks](https://hashnode.com/tag/microtasks)
-   [#event-loop](https://hashnode.com/tag/event-loop)
-   [#async-programming](https://hashnode.com/tag/async-programming)

## Written by

[Srekaravarshan N K](https://hashnode.com/@srekaravarshan)

@srekaravarshan

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

Frontend Developer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
