Books

System Design Workbook – Edição 2026 é uma obra que traduz, organiza e conecta os principais fundamentos da engenharia de sistemas distribuídos sob uma perspectiva prática, moderna e orientada à realidade de produção.

In this book, we are building a complete working server, and again we rebuild the whole thing on a different framework. It's about testing out a new approach. If the architecture is honest, the second version costs almost nothing and the business logic never moves. We ran the test, and I let you watch the result rather than describing it.

The latest version of WebAssembly has arrived and it has some really cool new features. I knew that I had to completely rewrite this book to make sure it was up to date. Now, here we are. Within this book, I will take you from the very basics of memory, control flow, and the mechanics that make Wasm work, through to compiling multiple languages, building multi-threaded applications, and optimising for real-world performance.

Another Production Field Manual: protect APIs before overload becomes an outage with rate limiting, throttling, and tenant fairness.

"Your systems are talking. Are you listening?"In a world where downtime costs millions and silent failures hide in plain sight, observability isn’t just a buzzword—it’s your superpower. But with hundreds of tools, frameworks, and metrics to choose from, how do you cut through the noise?Observability Tools: Design & Comparison Guide is your no-BS playbook to: ✅ Design observability pipelines tailored to AI/ML, microservices, and event-driven architectures. ✅ Compare the top 10 tools—from Datadog to Grafana Stack—and pick the perfect fit for your budget and scale. ✅ Avoid costly mistakes with red flags, alert fatigue fixes, and cost-saving strategies.

Rapid-development frameworks across Ruby on Rails, Node.js, PHP, Python, and .NET revolutionized how quickly we can ship software. But what happens when your business domain grows complex? Relying on Active Record and heavy ORM patterns tightly couples your database to your business logic. As your product matures, this coupling creates brittle, difficult-to-maintain codebases that resist change and slow down your team. The solution is the Domain Model Pattern (the foundation of Domain-Driven Design). It isolates business rules from infrastructure, creating a pure, scalable architecture. Historically, however, this pattern required a massive amount of effort and boilerplate, making it too slow for fast-paced development. That changes today. We are at an AI inflection point. Modern AI coding assistants excel at generating boilerplate and wiring infrastructure, effectively eliminating the traditional drawbacks of DDD. AI finally bridges the gap between the rapid speed of framework scaffolding and the architectural purity of a Domain Model. But to harness AI reliably, you cannot simply let it generate code unguided. You need a structured methodology to guide the machine. In this book, you will learn:How to build reliable, maintainable software using a strict, AI-assisted pipeline: Use Cases → Gherkin → Event Storming → Strategic & Tactical DDD.How to create implementation-agnostic class diagrams that serve as universal blueprints, allowing you to generate code in OOP languages (Java, C#, PHP, Python) or Functional languages (Elixir, Clojure, F#).How to future-proof your systems with a timeless methodology that prioritizes the longevity of business logic over the ephemeral nature of web frameworks.How to scale your architecture gracefully from a Majestic Monolith to Microservices without a complete rewrite. The methodology is language agnostics but in this edition all codes samples are in TypeScript. Whether you want to accelerate your development velocity, improve your system's resilience, or simply reclaim your craft by building beautiful, majestic systems, this book provides the blueprint.Discover how to combine the timeless principles of DDD with the power of AI.

From containers and Kubernetes to autoscaling, observability, Prometheus, Grafana, SLOs, security, and production failure. Volume III shows how distributed architecture becomes an operable, measurable, evidence-driven production system.

Cross the process boundary with a systems-level guide to concurrency, async I/O, IPC, TCP, TLS, HTTP/2, gRPC, retries, queues, consistency, observability, and the real cost of distribution.

Go beneath C# and .NET—from CPU, kernel, processes and threads to IL, JIT, native code, stacks, heaps and GC. Build the runtime mental model you need before deciding where, why, and whether a system should be distributed.

Migrating a stateless application to Google Cloud , think of it like moving to a new apartment: you need a plan, the right tools, and a clear understanding of where everything goes. "Migrating Stateless Workloads to Google Cloud: A Practical Guide for the Modern Developer" breaks down this process into 12 manageable steps, from assessing your current setup to post-cutover cleanup

Migrating stateful workloads to the cloud is like moving a fish tank—every detail matters. Unlike stateless applications, which can be redeployed with ease, stateful workloads demand careful handling to preserve data integrity, minimize downtime, and ensure a smooth transition.this guideis your practical guide to navigating this complex process.

Microservices aren't built with boxes on a diagram—they're built with owned truth, stable contracts, idempotent messages, and controlled failure.

Build financial systems that stay correct when requests repeat, events arrive late, and services fail. Learn practical patterns for money modeling, double-entry ledgers, idempotency, reconciliation, auditability, security, and invariant-driven testing—so every balance and transaction can be explained and trusted.

Stop overload from becoming unbounded queues, goroutines, and downstream calls. Build bounded backpressure that fails predictably.

It's a practical book. We're going to build something real together, a University API, and we're going to grow it chapter by chapter until it looks like a system you'd be proud to deploy. We'll start with a few endpoints, give it databases, make it concurrent, lock it down with authentication, wrap it in containers, and finally split it into cooperating services that talk over the network.