/Concurrency

How Concurrency Works: A Visual Guide

- Waqas Younas tl;dr: “Concurrent programming is hard. Mentally enumerating all the possible states that complex concurrent code might go through is far from easy. Visualizing concurrency can make it easier to understand how these programs operate, especially for those just beginning to learn about concurrency.”

featured in #579


Concurrency Diagrams

- Phil Booth tl;dr: “Concurrency diagrams are very simple and usually quick to create. They force you to put your assumptions in front of everyone to see, including yourself. Sometimes the act of creating a concurrency diagram can change your own mind about how different parts of a system should be sequenced. All you need are boxes, arrows and text.”

featured in #572


Scheduling Internals

- Tony Solomonik tl;dr: “I remember when I first learned that you can write a server handling millions of clients running on just a single thread, my mind was simply blown away. I used Node.js while knowing it is single threaded, I used async / await in Python, and I used threads, but never asked myself "How is any of this possible?". This post is written to spread the genius of concurrency and hopefully getting you excited about it too.

featured in #508


1,000,000 Concurrent Connections

- Joseph Mate tl;dr: "I hear the misconception that a server can only accept 65K connections or a server consumes a port for each accepted connection all the time." Joseph wrote this article to dispel this myth from 3 angles. 

featured in #308