The-Accidental-CTO README

The project's README from github.com/subhashchy/The-Accidental-CTO. As one markdown file: README.md.

The Accidental CTO

**How I Scaled from Zero to a Million Stores on Dukaan, Without a CS

I never set out to be a CTO. In fact, I didn’t even have a computer science degree. But somewhere between firefighting server crashes at 3 a.m. and obsessing over replication lag graphs, I found myself building systems that would eventually power over a million online stores at Dukaan.

This book, The Accidental CTO, is my behind-the-scenes account of that journey. It’s not a dry academic manual filled with abstract diagrams. Instead, it’s a story-driven handbook — one that mixes late-night startup battles with the hard system design lessons that only come from being in the trenches.

From scaling a scrappy MVP to running massive distributed pipelines, I’ll take you through the challenges we faced and the decisions that made (or nearly broke) us.


What You’ll Learn Inside


Why I Wrote This Book

I didn’t want to write another "theory of distributed systems" book. There are already plenty of those.

What I wanted to share is the practical side of system design — the part you only learn when a real company, with real customers and real money at stake, is on fire. The part where you’re not solving toy interview questions but dealing with:

This is the stuff no textbook teaches you.


Who This Book Is For

Whether you’re a software engineer, architect, or startup founder, I wrote this book to help you see distributed systems not as academic puzzles, but as living, evolving machines that you can actually build, operate, and grow.

If you’ve ever wondered how real companies actually scale — not in theory, but in practice — this is my candid, first-hand story.

And maybe, just maybe, you’ll find a bit of yourself in The Accidental CTO.

The-Accidental-CTO (subhashchy/The-Accidental-CTO)

Searching Database…

What is this?This is 'The Accidental CTO', a story-driven system design handbook by Subhash Choudhary about scaling the Dukaan e-commerce platform from zero to over a million stores without a formal CS degree.
Is this a technical textbook or a personal story?It's a mix of both: a narrative memoir of real production fires at Dukaan combined with practical system design lessons, not a dry academic manual.
How is the book organized?It walks through scaling applications, when to use replication/sharding/caching/queues, observability as a survival tool, resilience engineering, the hidden costs of cloud infrastructure, and the consistency/availability/latency tradeoff triangle.
Does it focus on theory or on real production incidents?It deliberately skips toy interview-style problems and instead digs into real incidents like Kafka pipelines choking on a bad partition or a database replica lagging 10 minutes behind.
Who is this book written for?Software engineers, architects, and startup founders who want to see distributed systems as real operable machines rather than academic interview puzzles.
What is Dukaan?Dukaan is the online store platform the author scaled to over a million merchants, and its real production challenges form the backbone of the book's lessons.
Does the book cover cloud cost tradeoffs?Yes, it discusses how AWS bills can become a startup's biggest expense and when going self-hosted makes more sense.
What is the consistency/availability/latency triangle it mentions?It's the book's framing of the classic distributed-systems tradeoff: you can never fully win on all three, and real systems must choose which corner to sacrifice.
Is this a hands-on exercise book like an interview prep guide?No, it's built around narrated real incidents rather than practice problems, aimed at giving intuition for operating systems at scale.
Creator
subhashchy
Size
30.5 MB
Stars
3.9K
Updated
CommitApr 09
Age
1y
Commits · 90 Days