---
title: "Sachin Tolay (@tolaysachin) | Hashnode"
description: "I am here to share everything I know about computer systems: from the internals of CPUs, memory, and storage engines to distributed systems, OS design, block..."
url: "https://hashnode.com/@tolaysachin"
---

@tolaysachin

# Sachin Tolay

@tolaysachin · Burnaby · Joined June 2025

### [From Sessions to JWTs: How Distributed Systems Reshaped Identity](https://nihcas.hashnode.dev/from-sessions-to-jwts-how-distributed-systems-reshaped-identity?utm_source=hashnode&utm_medium=feed)

The evolution of identity mechanisms closely followed the evolution of distributed systems. This article walks through that progression and the problems each step tried to solve. Before Identity (Early–Mid 1990s) In early web applications, identity w...

6 min read · [nihcas.hashnode.dev](https://nihcas.hashnode.dev/from-sessions-to-jwts-how-distributed-systems-reshaped-identity?utm_source=hashnode&utm_medium=feed)

[Dec 15, 2025](https://hashnode.com/posts/from-sessions-to-jwts-how-distributed-systems-reshaped-identity/69407a969ce843f61dbc68e0)

### [Memory Models Explained: How Threads Really See Memory](https://nihcas.hashnode.dev/memory-models-explained-how-threads-really-see-memory?utm_source=hashnode&utm_medium=feed)

Modern processors and compilers aggressively reorder instructions to improve performance → a behavior we explored in detail in my previous article: Instruction Reordering: Your Code Doesn’t Always Run in the Order You Wrote It. To write correct concu...

5 min read · [nihcas.hashnode.dev](https://nihcas.hashnode.dev/memory-models-explained-how-threads-really-see-memory?utm_source=hashnode&utm_medium=feed)

[Aug 13, 2025](https://hashnode.com/posts/memory-models-explained-how-threads-really-see-memory/689c0a61cb6e565641c20d04)

### [Instruction Reordering: Your Code Doesn’t Always Run in the Order You Wrote It](https://nihcas.hashnode.dev/instruction-reordering-your-code-doesnt-always-run-in-the-order-you-wrote-it?utm_source=hashnode&utm_medium=feed)

When writing code, you naturally expect instructions to run one after the other in the exact order they appear. For example: x=1; y=2; You’d expect x = 1 to complete before y = 2 starts. But in reality, modern CPUs and compilers don’t always execute...

5 min read · [nihcas.hashnode.dev](https://nihcas.hashnode.dev/instruction-reordering-your-code-doesnt-always-run-in-the-order-you-wrote-it?utm_source=hashnode&utm_medium=feed)

[Aug 5, 2025](https://hashnode.com/posts/instruction-reordering-your-code-doesnt-always-run-in-the-order-you-wrote-it/68923331d9d47da9240db276)

### [Blocking vs Non-blocking vs Asynchronous I/O](https://nihcas.hashnode.dev/blocking-vs-non-blocking-vs-asynchronous-io?utm_source=hashnode&utm_medium=feed)

When a program performs I/O → like reading from a file or socket → two key questions arise: Does the program stop and wait for the data, or continue running? (Blocking vs Non-blocking IO) Does the program keep checking for the result, or get notifi...

4 min read · [nihcas.hashnode.dev](https://nihcas.hashnode.dev/blocking-vs-non-blocking-vs-asynchronous-io?utm_source=hashnode&utm_medium=feed)

[Jul 30, 2025](https://hashnode.com/posts/blocking-vs-non-blocking-vs-asynchronous-io/6889a6dd606c00d96a262f89)

### [Traditional IO vs mmap vs Direct IO: How Disk Access Really Works](https://nihcas.hashnode.dev/traditional-io-vs-mmap-vs-direct-io-how-disk-access-really-works?utm_source=hashnode&utm_medium=feed)

In our earlier deep dive into Direct Memory Access (DMA), we explored how data can bypass the CPU to move efficiently between storage and memory. In this article, we will break down and compare three major approaches to disk access: Traditional (Buf...

3 min read · [nihcas.hashnode.dev](https://nihcas.hashnode.dev/traditional-io-vs-mmap-vs-direct-io-how-disk-access-really-works?utm_source=hashnode&utm_medium=feed)

[Jul 20, 2025](https://hashnode.com/posts/traditional-io-vs-mmap-vs-direct-io-how-disk-access-really-works/687d47501d8c1c24708b0062)
