Code-First Reliability: 4 Unconventional Approaches to Always-On Payments

This is Code-First Reliability.

Who is it for?

This book is aimed at engineers who want to keep up with the high standards imposed by payments processing.

What's included?

Concise and actionable advice in the form of 4 useful, though unconventional strategies to achieve reliability. Kubernetes is never mentioned, not even once.

Why should I read it?

Reliability and correctness are the most important properties of systems that process payments. And, while much has been written about how to write correct code, reliability is an afterthought, often left as an exercise for system administrators and SRE teams.

That might work in other industries, but not in payments. This book explains why, and explores 4 strategies to achieve high reliability that have nothing to do with standard reliability practices. They are code-first, not infrastructure-first.