Skip to main content
Toggle menu
Cracking
Walnuts
Interviews
Interview Roadmap
Start here
Pick your level, get your full prep plan
Case Studies
Full systems, worked end to end
HLD Playbooks
A full problem, step by step
Design Drills
One decision at a time, drilled
Compare Technologies
Which cache, queue or database, and why
LLD Problems
Object-oriented design rounds
DSA Templates
Patterns & templates in 5 languages
Cheat Sheets
Quick-ref for interviews
Behavioral
Fresher to Principal
Company Playbooks
MAANG and AI labs, by level
Staff+ Interviews
Staff/principal rounds
Forward Deployed Engineer
The FDE role and its decomposition round
AI
AI Engineering
LLM fundamentals, internals, inference, RAG
Math for AI
The math behind LLMs, with small numbers
Security
Security
AppSec to cloud to architecture, attacker-first
AI Security
LLM, RAG, agent, and MCP security
Engineering
API Design
REST, HTTP semantics, OpenAPI & versioning
Concurrency
Java, Python & Go
Performance Eng
Latency, percentiles, profiling & labs
Networking & Protocols
TCP, HTTP, TLS & more
Linux Internals
Kernel & system internals
Distributed Systems
Consensus & replication
Infrastructure
Production infra & ops
Key Technologies
Core tech deep dives
Database Internals
How every engine works inside
Cryptography
How HTTPS, TLS, passkeys, and PQC work
DevOps Internals
How Kubernetes, Terraform, and the stack work
Blockchain Engineering
Bitcoin, Ethereum, consensus, L2s and ZK
Leadership
Arch Decisions
ADRs & trade-offs
Platform Eng
Internal dev platforms
Incident Patterns
Postmortems & SRE
Metrics & FinOps
DORA, cost & KPIs
Compliance
Security & governance
Leadership
Tech lead & influence
Org Design
Team topologies & orgs
More
Posts
System design deep-dive topics
Visualizers & Calcs
Interactive system design tools
Whitepapers
Academic & industry papers
Books
Beyond-the-code reading picks
Search...
Ctrl+K
Go Premium
Log in
C
r
a
c
k
i
n
g
W
a
l
n
u
t
s
Compare
/
Distributed SQL
Spanner, CockroachDB, YugabyteDB, TiDB or Aurora DSQL: which one takes the orders past one writer?
Premium
Every product drawn against the same problem, with the sources next to each claim.
Loading…
Inside the full comparison
6 questions to ask first, each pointing at the products it favours
5 problems from the shop, drawn with no product and then once for each of the 5 products: 30 drawings
One drawing of how each of the 5 products is built, with what a read and a write do inside it and what limits it
12 more things compared, one short answer per product, with 85 checked claims and 20 warnings
2 scenarios, Past one writer and Keep Postgres, each showing how a changed requirement affects the choice or design
The interview answer in four moves, filled in for this family
122 vendor pages checked in 2026-09, linked next to every claim