vasanthk

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

indraniel

package main

import (
	"archive/tar"
	"compress/gzip"
	"flag"
	"fmt"
	"io"
	"os"
)

indiejoseph

阿爸	a1'ba4	18137
阿昌族	a1'chang1'zu2	50849
阿斗	a1'dou3	42632
阿飞	a1'fei1	48603
阿富汗	a1'fu4'han4	3461
阿訇	a1'hong1	34432
阿拉伯数字	a1'la1'bo2'shu4'zi4	35937
阿拉伯语	a1'la1'bo2'yu3	30476
阿妈	a1'ma1	16220
阿门	a1'men2	47913

jboner

Latency Comparison Numbers (~2012)
----------------------------------
L1 cache reference                           0.5 ns
Branch mispredict                            5   ns
L2 cache reference                           7   ns                      14x L1 cache
Mutex lock/unlock                           25   ns
Main memory reference                      100   ns                      20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy             3,000   ns        3 us
Send 1K bytes over 1 Gbps network       10,000   ns       10 us
Read 4K randomly from SSD*             150,000   ns      150 us          ~1GB/sec SSD