书籍 Microservice Patterns的封面

Microservice Patterns

Chris Richardson

出版社

Manning

出版时间

2017-09-01

ISBN

9781617294549

评分

★★★★★

标签

编程

书籍介绍

The monolithic architecture works well for small, simple applications. However, successful applications have a habit of growing. Eventually the development team ends up in what is known as monolithic hell. All aspects of software development and deployment become painfully slow. The solution is to adopt the microservice architecture, which structures an application as a services, organized around business capabilities. This architecture accelerates software development and enables continuous delivery and deployment of complex software applications.

Microservice Patterns teaches enterprise developers and architects how to build applications with the microservice architecture. Rather than simply advocating for the use the microservice architecture, this clearly-written guide takes a balanced, pragmatic approach. You'll discover that the microservice architecture is not a silver bullet and has both benefits and drawbacks. Along the way, you'll learn a pattern language that will enable you to solve the issues that arise when using the microservice architecture. This book also teaches you how to refactor a monolithic application to a microservice architecture.

目录
1. ESCAPING MONOLITHIC HELL
2. DECOMPOSITION STRATEGIES
3. INTER-PROCESS COMMUNICATION IN A MICROSERVICE ARCHITECTURE
4. MANAGING TRANSACTIONS WITH SAGAS
5. DEVELOPING BUSINESS LOGIC FOR MICROSERVICES

显示全部
用户评论
干货有,但啰嗦是真啰嗦,适合速读
《微服务架构设计模式》 https://book.douban.com/subject/33425123/
3.5/5;有收获但是收获不如预期。一些基础的内容日常开发已经接触的非常多了,而对于类似 saga pattern 这样的新鲜货,书上概念堆砌太多,等到要看具体实践步骤时给你的又是比钢板还厚的Java封装。。。这大概是我非常不喜欢Java的一点原因
虽然不喜欢用 Java 表达,但是重点是背后的思想和设计,总体说来还是比较明晰的
基本看完一遍了,总体感觉还是很不错的,各个模式讲解的比较深入,例子也容易上手
精读了前九章,但感觉读完还是不能清晰地说出"微服务"的定义是什么... 全书的思路:单体应用有哪些问题 => 服务拆分可以解决这些问题(按业务逻辑拆、按子域拆) => 微服务拆分必然导致跨进程调用(RPC/MQ) => 跨进程调用引入数据一致性保障问题:分布式事务 => Saga实现分布式事务 => Saga的基础上,DDD实现业务逻辑(聚合+领域事件) => 写场景:DDD的基础上,不再直接处理逻辑,而是通过process(并不处理真正的状态变更,只是生成对应的事件)+apply(将事件应用到聚合上)的方式 《事件溯源架构》=> 读场景(API组合、CQRS) 还是没太get到,为什么事件驱动架构会这么火,但是看起来又似乎没人在用?
大部分东西都知道了,没有太大的心意。新手看看还是不错的