Building Distributed Systems in the Age of AI Designing Intelligent, Resilient Architectures (Max Hopei) (z-library.sk, 1lib.sk, z-lib.sk)

【One-Line Pitch】 A forward-looking architecture guide for engineers who must keep building reliable distributed systems while AI shifts from a feature to a runtime participant. Read it if you design microservices, streaming pipelines, or agent-based platforms and need a vocabulary for the machine-centric era. 【Book Arc】 - **Opening (~0%–10%)**: Frames the core thesis — AI as a runtime component, not a feature — and reopens classical patterns (microservices, event-driven, reactive) for reinterpretation. Also sets expectations for the engineer's evolving role. - **Early (~10%–32%)**: Revisits microservice architecture through domain-driven vs. process-driven separation, layered applications, and invoker/use-case structure, then moves into message-driven architecture: message types (command, job, event, notification), versioning, and enterprise integration patterns. - **Middle (~32%–48%)**: Shifts to streaming architecture — windows, watermarks, late data, observability, cost control — and connects streaming to AI/ML use cases like recommendations and anomaly detection. Introduces agentic architecture: agent loops, tool calling, prompts, memory, RAG, embeddings, and vector databases. - **Late (~48%–70%)**: Deepens agentic design with security concerns (prompt injection, misuse, sensitive information disclosure), agentic platforms, multi-agent orchestration vs. choreography, and inter-agent communication. - **Ending (~70%–100%)**: Moves to the ecosystem level — the machine-centric Internet, where agents consume content and activate APIs. The excerpts do not cover the closing chapters in detail, so the final synthesis of privacy, protocols, and dual human/machine audiences is only partially visible. 【Key Takeaways】 - **AI is becoming a runtime participant, not a feature toggle** (Opening): This reframing forces architects to reconsider latency, failure modes, and observability for components that reason rather than just compute. - **Classical patterns still matter, but their contracts change** (Early): Microservice separation (domain-driven vs. process-driven) and message typing (command/job/event/notification) remain the vocabulary, but agentic systems turn messages into conversation and reasoning chains. - **Streaming correctness depends on time semantics** (Middle): Watermarks, windows, and late-data handling are the mechanisms that make unbounded streams trustworthy; without them, AI/ML pipelines silently degrade. - **Streaming observability and cost are first-class design concerns** (Middle): Lag, backpressure, checkpoint health, retention, and fan-out must be visible and tunable, or SLOs and bills both surprise you. - **Agent architecture is a loop with memory, tools, and retrieval** (Middle): Tool calling, role-tagged conversation history, RAG, embeddings, and vector databases form the practical building blocks — and each adds latency and failure surface. - **Agent security is a distinct threat model** (Late): Prompt injection, agent misuse, and sensitive information disclosure require new safeguards that classical input validation does not cover. - **Multi-agent systems need orchestration or choreography decisions early** (Late): Choosing between centralized orchestration and decentralized choreography shapes communication, debugging, and resilience. - **The Internet now serves two audiences** (Ending): Humans and machine agents have different expectations for interfaces, protocols, and privacy — systems must be designed for both. 【Reading Tips】 - **Deep-read Chapters 2–3** if you already know microservices; the value is in how the author reinterprets familiar patterns for AI-era contracts, not in the basics. - **Skim the streaming chapter's ML examples** if you work in streaming already; focus instead on watermark/late-data mechanics and the observability/cost checklist. - **Treat the agentic chapter as the pivot point**: read the agent loop, tool calling, and memory sections carefully — they are the conceptual bridge to multi-agent and security discussions. - **Use the security section as a design review checklist**: prompt injection and sensitive information disclosure are easy to underestimate until you map them to your own tool-calling surfaces. - **Keep a running list of "two-audience" decisions** (APIs, protocols, privacy) as you read the ending; the excerpts are thin there, so your own system context fills the gap. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book in detail, with the ending chapters only partially represented. Specific closing arguments about privacy-preserving infrastructure, protocol evolution, and the machine-centric Internet are therefore summarized at a high level rather than fully synthesized.