---
title: "Srekaravarshan N K (@srekaravarshan) | Hashnode"
description: "Frontend Developer. Read the latest articles by Srekaravarshan N K on Hashnode."
url: "https://hashnode.com/@srekaravarshan"
---

@srekaravarshan

# Srekaravarshan N K

@srekaravarshan · Joined January 2024

Frontend Developer

### [How a Transaction We Forgot to Close Took Down a Service](https://srekaravarshan.hashnode.dev/transaction-leak-connection-pool-outage?utm_source=hashnode&utm_medium=feed)

A survey API went down at 155 requests a minute while the database sat idle. The cause was a transaction we opened and never closed.

4 min read · [srekaravarshan.hashnode.dev](https://srekaravarshan.hashnode.dev/transaction-leak-connection-pool-outage?utm_source=hashnode&utm_medium=feed)

[Aug 13](https://hashnode.com/posts/transaction-leak-connection-pool-outage/6a7da14d41767cf0e58b2e58)

### [Part 7: Closing the Loop](https://srekaravarshan.hashnode.dev/event-loop-closing-the-loop?utm_source=hashnode&utm_medium=feed)

async/await is a state machine V8 compiles. requestAnimationFrame fires inside rendering. React 18 yields via MessageChannel. The full picture.

23 min read · [srekaravarshan.hashnode.dev](https://srekaravarshan.hashnode.dev/event-loop-closing-the-loop?utm_source=hashnode&utm_medium=feed)

[Jul 11](https://hashnode.com/posts/event-loop-closing-the-loop/6a52268f299eb69020186bdf)

### [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.

28 min read · [srekaravarshan.hashnode.dev](https://srekaravarshan.hashnode.dev/event-loop-microtasks-and-why-two-queues?utm_source=hashnode&utm_medium=feed)

[Jul 11](https://hashnode.com/posts/event-loop-microtasks-and-why-two-queues/6a52253510439b83c9e9daf0)

### [Part 5: The Event Loop, Mechanically](https://srekaravarshan.hashnode.dev/part-5-the-event-loop-mechanically?utm_source=hashnode&utm_medium=feed)

The HTML spec defines the event loop in 10 steps. Most developers have never read it. Plus: how Chromium integrates it with epoll.

27 min read · [srekaravarshan.hashnode.dev](https://srekaravarshan.hashnode.dev/part-5-the-event-loop-mechanically?utm_source=hashnode&utm_medium=feed)

[Jul 11](https://hashnode.com/posts/part-5-the-event-loop-mechanically/6a5223d24bf4499dabf8ddd1)

### [Part 4: Where JavaScript Actually Runs](https://srekaravarshan.hashnode.dev/event-loop-where-javascript-actually-runs?utm_source=hashnode&utm_medium=feed)

V8 is not a separate program — it's a library Chrome calls. The CPU never executes JavaScript text. Here's what actually runs when your code runs.

29 min read · [srekaravarshan.hashnode.dev](https://srekaravarshan.hashnode.dev/event-loop-where-javascript-actually-runs?utm_source=hashnode&utm_medium=feed)

[Jun 17](https://hashnode.com/posts/event-loop-where-javascript-actually-runs/6a330d4aea1e89894c5c934e)
