#goroutines articles

Go Concurrency Under the Hood - Goroutines

When you first start with Go from the Node.js world, all the cool async I/O with an event loop seems to be missing. You just write this "I/O blocking" code exactly like a synchronous procedure call: q

wpding.hashnode.dev

Lakshay DhoundiyalOct 15 · 9 min read

100,000 Requests. One Go Server. When Does Concurrency Become the Bottleneck?

🚨 The Traffic Spike: Everything Was Fine Until It Wasn't Imagine you've deployed a Go API. It handles user logins, fetches profile data, and returns responses in milliseconds. Everything looks health

lakshaydhoundiyal.hashnode.dev

Dhawal PandyaJun 6 · 8 min read

A Million Concurrent Things

"Concurrency is not parallelism." Rob Pike Go lets you write this: go doSomething() One word. That is all it takes to spin up a concurrent unit of execution. You can do this a hundred thousand times

dhawalpandya01.hashnode.dev

Priyanshu JajalJun 2 · 6 min read

Escape Analysis in Go

I was deep in building my Go HTTP Server - the one where I bypassed net/http entirely and built a multi-threaded engine from raw TCP sockets; when I wrote this line inside the POST handler: bodyBytes

priyanshujajal.hashnode.dev

Harrison GuoMay 14 · 18 min read

Channels Aren't Message Passing — How Parked Goroutines OOM-Killed a Pod

It's 3am. The Kafka consumer pod that's been running cleanly for six weeks gets OOM-killed. Kubernetes restarts it. Five minutes later: OOM-killed again. Restart. OOM-killed a third time. By the fourt

harrisonsec.hashnode.dev

Abhishek SharmaMay 5 · 7 min read

I Needed to Send an HTTP Request Without Slowing Down My API. Goroutines Fixed That.

In Part 12, I added resilience patterns — retry, timeout, circuit breaker. My backend could now survive Redis going down. But there was still a problem. When someone created an entry, I needed to notify an external service. A webhook: fire an HTTP PO...

abhishekshr.hashnode.dev

Sagar DasApr 26 · 11 min read

How Go's Scheduler Actually Works: A Deep Dive into the GMP Model

You’ve probably heard that goroutines are “lightweight threads.” But what does that actually mean? How does Go run millions of goroutines on just a handful of OS threads? The answer is the GMP schedul

go-stack-trace.hashnode.dev

Harrison GuoApr 16 · 7 min read

Why Go Handles Millions of Connections: User-Space Context Switching, Explained

Somewhere around 40,000 concurrent connections, your Java service falls over. Not from CPU, not from network — from memory, because every connection is a thread and every thread wants its own megabyte of stack. By the time you've finished Googling wh...

harrisonsec.hashnode.dev

Rohit LokhandeMar 4 · 8 min read

Listen, React, Repeat: Practical select Techniques in Go

Concurrency is one of Go’s greatest strengths, and channels are the backbone of safe communication between goroutines. But what happens when a goroutine needs to listen to multiple channels simultaneo

blog.rohitlokhande.in

Anish RoyFeb 18 · 5 min read

Process, Threads and Goroutines

What Is a Process? A program is an executable file on disk. When the operating system loads that file into memory and starts execution, it becomes a process. A process has its own: Memory Address Registers Program Counter Stack and Heap memory ...

devdump.tech

Search Hashnode

Trending tags this week