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.
A Briefing about what is micro-service and potential challenges for adopting microservice architecture from technical, human-mind and team-organization perspective.
PS: 这不是一本详细的microservice hands-on的...A Briefing about what is micro-service and potential challenges for adopting microservice architecture from technical, human-mind and team-organization perspective.
PS: 这不是一本详细的microservice hands-on的书，但是在做任何事之前，先高屋建瓴地了解其所历史及所带来的变化，这个是必要的。短评里给差评的出发点压根就不对。(展开)
当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版
莫冲
人民邮电出版社2016版
pan
人民邮电出版社2016版
1 有用 LipingTaBaBa 2016-12-24
典型ThoughtWorks的风格, 都是扯淡的废话, 浪费时间.
0 有用 andyh 2016-12-03
定义 service boundary 是最难的，即怎么拆的问题。
0 有用 拉脚 2017-01-16
nice high level guidance, more about general thoughts than practice
0 有用 aleung 2016-10-13
全面系统的介绍了构建微服务系统需要考虑的方方面面
0 有用 粗人 2018-05-14
没事多翻翻 不至于迷失在operational overhead中 对底层人员的指导意义更在于理解为什么要这么做以及理想的情况该是怎样 但是在公司范围内没有统一标准的情况下 很多decision making就变成了based on个人意愿的所谓best practice而不是铁打铁金科玉律 难
0 有用 Aquietzero 2019-07-25
主要介绍概念与原则，里面说到的工具也很老旧。很多地方提到现实会更为复杂，没有既定的通用方法，这是实话，但这同时意味着本书效用大减。以作者的资历与经验，倒不如以一个详细例子贯穿全书更好～
0 有用 露秋 2019-06-19
讲解的很详细，能从大局观上认识微服务
0 有用 吃豆子的鱼 2019-06-18
由前人宝贵经验总结出的最佳实践，颇具指导意义。
0 有用 小芝士蛋糕 2019-05-19
结合实际项目阅读，有一定收获。知识比较笼统，比较泛。都是软件项目经验之谈，对很多新兴的软件工程实践进行了很好的总结和概念化。 让你在各种工程设计讨论中理论知识加持，信心倍增——纸上得来终觉浅，绝知此事要躬行
0 有用 自拍的梵谷 2018-11-29
A Briefing about what is micro-service and potential challenges for adopting microservice architecture from technical, human-mind and team-organization perspective. PS: 这不是一本详细的microservice hands-on的... A Briefing about what is micro-service and potential challenges for adopting microservice architecture from technical, human-mind and team-organization perspective. PS: 这不是一本详细的microservice hands-on的书，但是在做任何事之前，先高屋建瓴地了解其所历史及所带来的变化，这个是必要的。短评里给差评的出发点压根就不对。 (展开)