READINGS.

No Reviews Yet

I read this book after Designing Data-Intensive Applications, where, as I said:

“You’ll come across a problem and think, ‘Ah, there is a thing for this.’ And yes, that thing is probably in this book.”

Software Architecture: The Hard Parts is almost the opposite.

It gives you a different feeling:

“Ah, I know there is a thing for this—but is that thing actually the right solution here?”

And that’s pretty much what this book is about: not learning what solutions exist, but learning how to reason about which solution fits the problem.

P.S. I loved the SysOps Squad saga!

This book is Martin Kleppmann’s way of saying:

“You don’t know shit, but I’ll teach you.”

Sometimes you’ll think you didn’t understand anything, even after revisiting a chapter a couple of times. But later, you’ll come across a problem and think:

“Ah, there is a thing for this.”

And yes, that thing is probably in this book.

I enjoyed every chapter, and I genuinely felt like a different engineer after reading it.

Nothing much to say it’s almost an industry standard.

It gives you a clear idea that code is an abstraction, and it’s written for humans.

Don’t try to be clever. Make it easier for the next person to understand, because that person could be you six months later.

Sometimes you build systems and there is an urge you follow. Your gut tells you thats feels like the right thing to do.

Yet you don’t know if it’s a real-world pattern or just something you came up with.

Then you realize other people have faced similar problems and found similar solutions.

Designing Distributed Systems is like a cookbook for that. It gives you solid recipes and patterns to apply when needed—and, more importantly, helps you understand when you actually need them.

No Reviews Yet

No Reviews Yet