Over the past 10 years, distributed systems have become more fine-grained. From the large multi-million line long monolithic applications, we are now seeing the benefits of smaller self-contained services. Heavy-weight, hard to change Service Oriented Architectures are not the answer; instead we are now seeing finer-grained systems consisting of collaborating microservices. Eas...
Over the past 10 years, distributed systems have become more fine-grained. From the large multi-million line long monolithic applications, we are now seeing the benefits of smaller self-contained services. Heavy-weight, hard to change Service Oriented Architectures are not the answer; instead we are now seeing finer-grained systems consisting of collaborating microservices. Easier to change, deploy, and if required retire, organizations which are in the right position to take advantage of them are yielding significant benefits.
This book takes an holistic view of the things you need to be cognizant of in order to pull this off. It covers just enough understanding of technology, architecture, operations and organization to show you how to move towards finer-grained systems.
作者简介
· · · · · ·
Sam Newman is a technologist at ThoughtWorks, where he currently splits his time between encouraging and sharing Innovation globally and helping design and build their internal systems. He has worked with a variety of companies in multiple domains around the world, often with one foot in the developer world, and another in the IT operations space. If you asked him what he does,...
Sam Newman is a technologist at ThoughtWorks, where he currently splits his time between encouraging and sharing Innovation globally and helping design and build their internal systems. He has worked with a variety of companies in multiple domains around the world, often with one foot in the developer world, and another in the IT operations space. If you asked him what he does, he’d say ‘I work with people to build better software systems’. He has written articles, presented at conferences, and sporadically commits to open source projects. He is currently writing a book, Building Microservices, which should be available in the Autumn of this year from O'Reilly.
Microservices is a sexy concept, but for quite a long time, I don’t exactly know what it is, and how it work to help my daily job, read this book for clarify it. This book is a guidance, not a practic...Microservices is a sexy concept, but for quite a long time, I don’t exactly know what it is, and how it work to help my daily job, read this book for clarify it. This book is a guidance, not a practice, most suit for reading by architect and develop manager(展开)
当PaaS（Platform as a service）已不是什么新鲜名词的时代，我们每天面对这各种各样的新兴技术名词，哪怕作为一名所谓的业内人士，我已然清晰地记得当2017年初的某个初晨，工位隔壁的同事兴奋地对我说“Hi，Bill 听说北京团队开始做FaaS了”时自己的一脸懵逼，心里暗想什么是F...
(展开)
I have seen many teams adopt a model of shared service ownership. I find this approach suboptimal...One key reason people move toward shared services is to avoid delivery bottlenecks. What if there is a large backlog of changes that need to be made in a single service?...There is another model that could work well for us, though.... 答案就是内部开源。
2015-12-08 15:02
I have seen many teams adopt a model of shared service ownership. I find this approach suboptimal...One key reason people move toward shared services is to avoid delivery bottlenecks. What if there is a large backlog of changes that need to be made in a single service?...There is another model that could work well for us, though....引自 第10章
康威法则的原文： Any organization that designs a system (defined more broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization’s communication structure.
2015-12-08 14:14
康威法则的原文：
Any organization that designs a system (defined more broadly here than just
information systems) will inevitably produce a design whose structure is a copy of the
organization’s communication structure.引自 第10章
I have seen many teams adopt a model of shared service ownership. I find this approach suboptimal...One key reason people move toward shared services is to avoid delivery bottlenecks. What if there is a large backlog of changes that need to be made in a single service?...There is another model that could work well for us, though.... 答案就是内部开源。
2015-12-08 15:02
I have seen many teams adopt a model of shared service ownership. I find this approach suboptimal...One key reason people move toward shared services is to avoid delivery bottlenecks. What if there is a large backlog of changes that need to be made in a single service?...There is another model that could work well for us, though....引自 第10章
康威法则的原文： Any organization that designs a system (defined more broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization’s communication structure.
2015-12-08 14:14
康威法则的原文：
Any organization that designs a system (defined more broadly here than just
information systems) will inevitably produce a design whose structure is a copy of the
organization’s communication structure.引自 第10章
I have seen many teams adopt a model of shared service ownership. I find this approach suboptimal...One key reason people move toward shared services is to avoid delivery bottlenecks. What if there is a large backlog of changes that need to be made in a single service?...There is another model that could work well for us, though.... 答案就是内部开源。
2015-12-08 15:02
I have seen many teams adopt a model of shared service ownership. I find this approach suboptimal...One key reason people move toward shared services is to avoid delivery bottlenecks. What if there is a large backlog of changes that need to be made in a single service?...There is another model that could work well for us, though....引自 第10章
康威法则的原文： Any organization that designs a system (defined more broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization’s communication structure.
2015-12-08 14:14
康威法则的原文：
Any organization that designs a system (defined more broadly here than just
information systems) will inevitably produce a design whose structure is a copy of the
organization’s communication structure.引自 第10章
juvenxu
人民邮电出版社2016版
Asura
人民邮电出版社2016版
莫冲
人民邮电出版社2016版
pan
人民邮电出版社2016版
甲烷菌。
人民邮电出版社2016版
Quiet Time
人民邮电出版社2016版
0 有用 丸子 2017-08-09
信息量很大，涵盖推进微服务的各个阶段的细节，虽然都是理论，但是能很好的理清思路。
0 有用 北雪_TIG 2016-10-30
"Sometimes memory is good enough. Other times you need to know if it has changed."
0 有用 马文 2018-09-10
Microservices is a sexy concept, but for quite a long time, I don’t exactly know what it is, and how it work to help my daily job, read this book for clarify it. This book is a guidance, not a practic... Microservices is a sexy concept, but for quite a long time, I don’t exactly know what it is, and how it work to help my daily job, read this book for clarify it. This book is a guidance, not a practice, most suit for reading by architect and develop manager (展开)
0 有用 小芝士蛋糕 2019-05-19
结合实际项目阅读，有一定收获。知识比较笼统，比较泛。都是软件项目经验之谈，对很多新兴的软件工程实践进行了很好的总结和概念化。 让你在各种工程设计讨论中理论知识加持，信心倍增——纸上得来终觉浅，绝知此事要躬行
0 有用 d0ngw 2015-05-27
中规中矩的一本书
0 有用 jlinKnight 2020-10-19
这本书对microservice的本质，还有service之间的interaction有很好的阐述。微服务架构是当下互联网最火热的技术，也需要大量的实践来总结经验
0 有用 而功力不唐捐 2020-08-14
From: 2020-07-06 End: 2020-08-14 大概花了一个月时间，正好公司的读书会也选了这本书。主要是些知识经验的分享，另外现在是2020年，成书时间是2015年，技术领域5年前已经是很久之前的事情了。有些东西已经变化了。 从4月开始到现在，大概4个多月的时间，没有看docker/kubernetes等平台相关的书，但是实际上为了充分利用资源，还是应该回到4月前看的书。
0 有用 Aquietzero 2019-07-25
主要介绍概念与原则，里面说到的工具也很老旧。很多地方提到现实会更为复杂，没有既定的通用方法，这是实话，但这同时意味着本书效用大减。以作者的资历与经验，倒不如以一个详细例子贯穿全书更好～
0 有用 露秋 2019-06-19
讲解的很详细，能从大局观上认识微服务
0 有用 吃豆子的鱼 2019-06-18
由前人宝贵经验总结出的最佳实践，颇具指导意义。