Distributed systems don't fail politely. A network partition doesn't send a warning. A crashed node doesn't explain itself. And when milliseconds matter, a single unnecessary memory copy can be the difference between a system that meets its promise and one that quietly breaks it. C++ remains the language of choice for engineers who need to control exactly what their code does, down to the memory layout - and this book shows you how to put that control to work building systems that stay correct and stay fast under real, unpredictable failure.Picture this: your system passes every test. It works flawlessly in staging. Then it goes live - and under real traffic, at 2 a.m., something breaks in a way no test ever caught. A lock you didn't know was contended. A clock you assumed was in sync. A network you trusted to just work.This book exists because that moment is avoidable.You'll learn to see the failure before it happens - to ask the right question at design time instead of debugging the wrong answer in production. By the time you reach the final chapter, you won't just understand distributed systems theory. You'll have built one, watched it survive a node crash, and measured, with your own numbers, exactly how fast it really is.What's Inside- The theory that actually matters - CAP, PACELC, and FLP, translated into decisions you'll actually make- Modern C++ done right - ownership, the memory model, atomics, and compile-time performance techniques- Concurrency without the guesswork - locks, lock-free structures, coroutines, and the NUMA-level details most books skip- Networking built for speed - sockets, epoll, io_uring, and a hand-built RPC layer- Consensus, demystified - a full, working Raft implementation in C++, not just a description of one- Fault tolerance and observability - failure detection, graceful degradation, tracing, and tail-latency metrics- A complete capstone - a distributed, fault-tolerant key-value store, built chapter by chapter and benchmarked at the endThis book is for the intermediate-to-advanced C++ developer who already writes working code and now wants to write code that survives contact with the real world - engineers building backend infrastructure, database internals, or anything where "it works on my machine" isn't good enough. You should be comfortable with C++ fundamentals already; this book will take you the rest of the way, from a single competent process to a fleet of them working together correctly.Every distributed system you've ever used - the one processing your payment, routing your message, holding your data - was built by someone who had to learn exactly what's in this book, usually the hard way, usually in production. You don't have to.Turn the page, and start building the system that doesn't go down.
Prijshistorie
* Prijshistorie bevat geen data van Amazon, Amazon Marketplace.
Prijzen voor het laatst bijgewerkt op: