This comprehensive guide helps developers and architects understand current cloud-native technologies, with recommendations that explain when you need to use each one. Authors Boris Scholl, Trent Swanson, and Peter Jausovec describe the patterns you need for building cloud-native applications, and provide best practices for the most common tasks such as messaging, eventing, and DevOps.
This practical book also delivers an architectural blueprint for a modern cloud-native application. You’ll learn about microservices, containers, serverless computing, storage types, data considerations, portability, and the use of functions.
Differentiate between containers and functions, and understand when to use which technology
Leverage Service Meshes to move complexity, such as distributed tracing and mutual TLS handshakes, away from the developer
Use messaging and eventing as the glue for the cloud-native composite applications
Handle state-in distributed applications
Understand what makes your application portable
Boris is a Product Architect with the Azure Compute team focusing on the next generation of distributed systems platforms and application models. He has been working on Azure Developer tools and platforms in various product engineering roles since 2011. Boris re-joined the Azure Compute team in 2018 after having spent the 18 months outside Microsoft leading an engineering team to work on a microservices platform based on Kubernetes and Service Meshes. His work on distributed systems platforms has resulted in several patents about cloud computing and distributed systems. Boris is a frequent speaker at industry events, a contributor to many blogs, instructor for distributed computing topics and the lead author of one of the first books about microservices and Docker on Azure (Microservices with Docker on Azure).
As a co-founder and consultant with Full Scale 180, he worked with some of Microsoft’s largest customers, helping them migrate and build applications on the Microsoft Azure platform. He has been involved in building some of the largest applications running on Microsoft Azure today, many of which are now utilizing Docker, serverless technologies, and a microservices architecture. Trent often works with the Microsoft Patterns and Practices team developing guidance and best practices for cloud applications where he also co-authored a book on cloud design patterns. As a co-founder of Krillan and Threadsoft he has built applications based on a microservices architectural style using Docker, Node.js, Go, and Mesos. As a co-founder of B & S Enterprises, he dabbles with various IoT technologies for commercial building management.
Peter Jausovec is a software engineer with more than 10 years of experience in the field of software development and tech. During his career, he spent time in various roles, starting with QA then moving to software engineering and leading tech teams. His early career was mostly focused on developer and cloud tooling for Azure while working for Microsoft. In recent years, he has been focusing more on developing distributed systems, working with cloud-native solutions and microservices platform developed on Kubernetes and service mesh.
评分
评分
评分
评分
这本书的语言风格简直是一场文学的盛宴,我甚至一度怀疑我拿错了一本前卫诗集而非技术读物。它的行文节奏变化莫测,时而如急流般奔涌,充斥着大量晦涩的古希腊哲学词汇与现代物理学的最新猜想的混搭;时而又如同深秋的湖面,寂静无声,只留下几句如同谶语般的简短陈述。比如,在论述“状态持久化”的章节里,作者没有提及任何数据库或存储引擎的名称,而是用了一整段篇幅来描述“记忆的不可靠性”与“时间箭头的单向性”如何共同塑造了我们对“永恒数据”的焦虑。这种高度的文学化处理,让阅读体验变得极度依赖读者的心境。在我情绪高昂、思绪开阔时,那些复杂的语句仿佛在我脑海中构建出清晰的图像;可一旦我略微分心,试图在其中寻找具体的代码示例或架构蓝图,立刻就会被那些华丽的辞藻和跨学科的跳跃所吞噬。我尝试用它来指导我最近的项目重构,结果发现,每当我需要一个“下一步该怎么做”的指示时,我得到的反馈却是对“行动的意义”的深刻反思,这无疑是一种高阶的、但对日常工作帮助有限的阅读体验。
评分这本书的作者似乎对主流的技术范式抱持着一种审慎的疏离感。通读下来,我没有找到任何对当前行业内热门框架、流行工具的肯定或批评,它完全置身于技术讨论的“场域”之外,专注于描绘一个更宏大、更具普适性的模型。它探讨了“系统的生命周期”如何模仿生物演化,从单细胞的复制到多器官的协同,这种类比的深度和广度令人叹服。书中多次引用了复杂的生物学和生态学模型来解释软件系统的行为,这使得整个论述充满了生命力,仿佛每一个微服务都是一个有机的细胞。然而,正因为这种高度的抽象和类比,使得这本书在解决实际问题时显得力不从心。例如,当我试图理解如何在一个大规模的微服务网络中实现有效的跨地域部署时,我从书中读到的是关于“物种迁徙的能量消耗模型”,这虽然在理论上优雅,但在实际的运维场景中,我更需要的是关于负载均衡和延迟优化的具体策略。总而言之,这是一本拓宽视野、重塑世界观的奇书,但它拒绝成为你工作台上的速查手册,它要求的是你放下手头的工作,去思考工作背后的“为什么”。
评分阅读这本书的体验,更像是在参与一场由作者主导的、关于“非决定性计算”的冥想训练。我注意到书中几乎没有出现任何图表、流程图,甚至连列表和要点总结都极其罕见。所有的知识点都以散文的形式铺陈开来,强调的是概念之间的流动性和模糊边界。我特别关注了其中关于“弹性设计”的部分,本以为会看到关于超时重试、熔断机制的深入讨论,结果书中讨论的是“系统对不确定性的接受程度”,以及如何通过引入“可控的随机性”来优化整体的性能指标。这种对概念的重塑令人耳目一新,但同时也带来了一个实际操作上的难题:如何将这种深奥的、几乎是哲学的“接受不确定性”转化为可部署、可测试的工程实践?书中对此避而不谈,仿佛在暗示,一旦你真正理解了这些概念的底层逻辑,工具和代码就成了自然而然的产物。这种极端的自洽性,使得这本书成为了一件艺术品,而非一本工具书,它要求读者付出极高的认知负荷去追随作者的思路,否则很容易迷失在那些关于“信息密度与可感知复杂性”的辩论之中。
评分这本书的封面设计着实吸引人,那种深邃的蓝与闪烁的星光交织在一起,让人联想到无垠的宇宙和未知的探索。我最初翻开它,是期待能在这浩瀚的知识海洋中找到一些关于构建未来系统的启发。然而,阅读过程中,我却发现它更像是一部哲学思辨录,探讨的更多是“存在”与“演化”的本质,而非具体的技术实践。作者用极其细腻的笔触描绘了复杂系统的自组织能力,特别是对混沌理论在软件架构中的隐喻运用,着实令人拍案叫绝。比如,书中花了大量的篇幅去解析一个假设的“零点服务”如何从随机噪声中涌现出稳定的通信协议,这部分叙述极其抽象,充满了比喻和象征,像是在阅读一部赛博朋克小说的高级理论章节。我反复咀嚼那些关于“熵减”与“信息拓扑”的论述,感觉自己像是站在一个巨大的齿轮旁,试图理解驱动这一切的底层逻辑,但每当感觉快要触及核心时,文字又巧妙地滑向了另一个更深层次的哲学困境。这本书无疑挑战了我的思维边界,但坦白说,对于一个渴望快速掌握工程技能的读者来说,它的“实操指南”部分几乎是缺失的,更多的是一种对“如何思考”的引导,这种引导既令人敬畏,也令人有些无助。
评分这本书的结构安排,说实话,给我一种故意为之的“反线性”观感。它似乎刻意避免了传统技术书籍那种“从基础到深入”的逻辑链条。相反,它像是一张巨大的蜘蛛网,各个章节之间相互指涉,却缺乏一个明确的起点或终点。我花了两天时间试图梳理出它的核心论点脉络,但每一次尝试都以失败告终。作者似乎认为读者已经完全掌握了所有基础知识,可以直接介入到对“系统之美学”的探讨中。例如,它在一开始就抛出了关于“分布式共识的形而上学基础”的讨论,这个主题本身已经足够庞大和复杂,而作者并未提供任何铺垫,直接将读者投入到这个深水区。这迫使我必须频繁地在不同章节间来回翻阅,试图寻找那些隐藏的、相互依赖的概念锚点。这种阅读过程充满了智力上的挫败感,但也夹杂着发现新大陆般的惊喜。它更像是一本需要被“体验”而不是“学习”的书,你需要接受它提供的碎片化信息,然后自己去缝合出一个属于你自己的理解框架,这对于习惯了清晰知识体系的读者来说,无疑是一种极大的挑战。
评分can be used as reference for aspect of building distributed system
评分can be used as reference for aspect of building distributed system
评分Good reference book. SY
评分can be used as reference for aspect of building distributed system
评分Good reference book. SY
本站所有内容均为互联网搜索引擎提供的公开搜索信息,本站不存储任何数据与内容,任何内容与数据均与本站无关,如有需要请联系相关搜索引擎包括但不限于百度,google,bing,sogou 等
© 2026 book.wenda123.org All Rights Reserved. 图书目录大全 版权所有