The book is here.

Two years, 740 pages, and the small Bengal cat who taught me what resilience really means… in life…

---

Today is not a normal issue of Failover Weekly. No Route 53 deep-dive, no BGP analysis, no architecture breakdown. Those will be back next week.

The book is finally here.

Cloud Networking and Resilience is officially live on Amazon. The paperback ships June 4th. To everyone who pre-ordered — thank you. Your copy is already on your device.

---

Why this book exists

I did not start writing because I had time. I started writing in 2024, almost two years ago, because of Ade.

Ade — Hades, in English — was my Bengal cat. My shadow. The teacher of everything I have ever understood about resilience. He absorbed everything life put in front me and i front of him and kept on being himself, quietly, completely. He was the resilience long before I had a chapter to name it.

When I lost him in July 2022, I did not know what to do with the grief. I started volunteering, helping cats in distress, making my life a mission to help those little souls in name of Ade. One day I thought I would have wanted the world to see him, see his eyes, feel the love and joy he brought into my life but I only knew the technical language I had spent twenty years learning. So that became the answer. The book is what I built with the only tools I had.

He is on the cover. He is in the dedication. Every royalty I earn from this book goes to charities supporting cats who suffered trauma and are in distress. If you buy it, you are not only buying a technical reference — you are turning it into help for the animals who need it.

What’s in 740 pages

✦ DNS resilience, failover, and Anycast routing

✦ BGP optimization, traffic engineering, and path-aware routing

✦ Cell-based architectures and fault isolation

✦ Multi-region and multi-cloud disaster recovery

✦ Continuous resilience testing and predictive AIOps

✦ DORA, NIS2, and operational resilience compliance

✦ Resilience tackled layer by layer — from physical links to microservices

Cloud-agnostic patterns, AWS as the reference implementation. For cloud architects, network engineers, SREs, and anyone who has been on the wrong side of a postmortem.

---

One idea from the book — before anyone else opens it

Here is the thesis that runs through every chapter.

Most teams treat resilience as something you bolt on after the system is built. You ship the architecture, then add the failover, then run a tabletop, then patch whatever the tabletop surfaces.

The book argues for the opposite. Resilience is not a property you add. It is a property you design for from the first diagram — at every layer, simultaneously.

If the physical layer fails and your application has no awareness, no graceful degradation, no shedding, the elegance of your Transit Gateway design will not save you. If your application is bulletproof but DNS serves a single stale answer at the wrong second, the same is true. Your weakest layer is your resilience ceiling.

The OSI-layer-by-layer structure of the book is not academic. It is the discipline that forces you to ask, for every system you operate: where exactly can this fail, and what does the next layer do when it does?

That is the question I wish someone had taught me to ask in 2005. The next twenty years would have looked very different.

---

How to order

Amazon ebook (live today):

https://www.amazon.com/dp/B0HLKKR1T1

Paperback and Apress edition (ships June 4):

https://link.springer.com/book/9798868824357

Companion repository:

https://github.com/Apress/Cloud-Networking-and-Resilience

Thank you!

Failover Weekly subscribers were the first audience for these ideas in their newsletter form. Many of you have been on this journey with me since the first issue. The book is what those ideas became when given the space they needed.

If you read it and find it useful, the kindest thing you can do is leave an honest review on Amazon — even one sentence helps the next reader find it.

And if you want to talk about it in person, I will be at AWS Summits and conferences over the coming months. Come find me.

— Cristian

P.S. Meet Ade. He is the reason this book exists.