所需积分/C币:16 2018-04-04 14:32:36 10.4MB PDF
收藏 收藏

Microservice architecture has emerged as a common pattern of software develop‐ ment from the practices of a number of leading organizations. These practices includes principles, technologies, methodologies, organizational tendencies, and cul‐ tural characteristics. Companies taking steps to implement microservices and reap their benefits need to consider this broad scope. Who Should Read This Book You should read this book if you are interested in the architectural, organizational, and cultural changes that are needed to succeed with a microservice architecture. We primarily wrote this book for technology leaders and software architects who want to shift their organizations toward the microservices style of application development. You don’t have to be a CTO or enterprise architect to enjoy this book, but we’ve writ‐ ten our guidance under the assumption that you are able to influence the organiza‐ tional design, technology platform, and software architecture at your company. What’s In This Book This book promotes a goal-oriented, design-based approach to microservice architec‐ ture. We offer this design-centric approach because, as we talked to several companies about their programs, we discovered one of the keys to their success was the willing‐ ness to not stick to a single tool or process as they attempted to increase their compa‐ ny’s time-to-market while maintaining—even increasing—their systems’ safety and resilience. The companies we talked to offered a wide range of services including live video and audio streaming service, foundation-level virtual services in the cloud, and support for classic brick-and-mortar operations. While these companies’ products vary, we learned that the principles of speed and safety “at scale” were a common thread. They ix each worked to provide the same system properties in their own unique ways—ways that fit the key business values and goals of the company. It’s the properties and values that we focus on in this book, and the p
Praise for microservice architecture The authors approach of starting with a value proposition,"Speed and Safety at Scale in Harmony, and reasoning from there, is an important contribution to thinking about application design - Mel Conway, educator and Inventor A well-thought-out and well-written description of the organizing principles underlying the microservices architectural style with a pragmatic example of pplying them in practice James lewis, Principal Consultant, Thought Works This book demystifies one of the most important new tools for building robust, scalable software systems at speed Otto Berkes, Chief Technology oficer, Ca Technologies If you ve heard of companies doing microservices and want to learn more, microservice Architecture is a great place to start. It addresses common questions and concerns about breaking down a monolith and the challenges you'll face with culture, practices, and tooling. The microservices topic is a big one and this book gives you smart pointers on where to go ne Chris Munns, Business Development Manager-DevOps Amazon web services Anyone who is building a platform for use inside or outside an organization should read this book. It provides enough a-ha insights to keep everyone on your team engaged, from the business sponsor to the most technical team member highly recommended! -Dave Goldberg, Director, API Products, Capital Or A practical roadmap to microservices design and the underlying cultural and organizational change that is needed to make it happen successfully. Mark Boyd, Writer/Analyst, Platformable An essential guidebook for your microservices journey, presenting the concepts, discussions, and structures supportive of this architectural pattern as well as the pragmatic ground work to become successfu lan Kelly, Experimenter and Contributor, CA Technologies Microservice architecture Aligning Principles, Practices, and Culture rakli nadareishvili, ronnie mitra Matt Mclarty, and Mike amundsen Beijing. Boston. Farnham. Sebastopol. Tokyo OREILLY Microservice architecture by irakli Nadareishvili, Ronnie Mitra, Matt Mclarty, and Mike amundsen Copyright C 2016 Mike Amundsen, Matt McLarty, Ronnie Mitra, Irakli Nadareishvili. All rights reserved Printed in the united states of america Published by o reilly Media, Inc, 1005 Gravenstein Highway North, Sebastopol, CA95472 O Reilly books may be purchased for educational, business, or sales promotional use. Online editions are alsoavailableformosttitles(http://safaribooksonline.com).Formoreinformationscontactourcorporate institutionalsalesdepartment800-998-9938orcorporate@oreilly.com Editors: Brian MacDonald and Holly bauer Indexer: Word Co Indexing Services, Inc Production editor: Kristen brown Interior Designer: David Futato Copyeditor: Christina Edwards Cover Designer: Karen Montgomery Proofreader: Kim Cofer llustrator: Melanie Yarbrough June 2016 First edition Revision History for the First Edition 2016-06-02: First Release 2016-07-18: Second release Seehttp://oreilly.com/catalog/errata.csp?isbn=9781491956250forreleasedetails The O reilly logo is a registered trademark of o reilly media, Inc. Microservice architecture, the cover mage and related trade dress are trademarks of o reilly media, Inc While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights 978-1-491-95625-0 Table of contents Preface Part 1. Understanding microservices 1. The Microservices Way....... Understanding Microservices Adopting microservices What are Dont i already have them? 6 How could this work here? How would we deal with all the parts? Who is in charge The Microservices Way The speed of change The Safety of Change 999 At scale 10 In harmony 10 Summary 2. The Microservices value proposition ,13 Microservice architecture benefits 13 Deriving Business value 15 Defining a Goal-Oriented, Layered Approach 17 Modularized microservice architecture Cohesive Microservice Architecture 18 Systematized microservice Architecture 18 Maturity Model for Microservice Architecture Goals and Benefits 19 Applying the Goal-Oriented, Layered Approach 20 Summary 21 Part II. Microservice Design Principles 3. Designing Microservice SystemS................ The Systems Approach to Microservices 25 Service 27 Solution 28 Process and tools 28 Organization 28 Culture 29 Embracing Change Putting it Together The Holistic System Standardization and coordination A Microservices Design Process 33 Set Optimization goals 34 Development Principles 35 Sketch the System Design Implement, Observe, and adjust 36 The Microservices System Designer 38 Summary 38 4. Establishing a Foundation 41 Goals and Principles Goals for the Microservices Way 42 Operating Principle Platforms 49 Shared capabilities Local Capabilities 52 Cultu Focus on Communication 5 alis gning Your leams 55 Fostering innovation 56 Summary 58 Part l. microservices in Practice 5. Service Desig 61 Microservice boundaries 62 Microservice Boundaries and Domain-Driven Design 62 Bounded context 64 Smaller is better Ubiquitous language 66 Table of contents API Design for Microservices Oriented 67 Hypermedia-Driven 68 Data and microservices Shipping, Event sourcing g System Model for Shipping, Inc CQRS 76 Distributed Transactions and Sagas Asynchronous Message-Passing and microservices 80 Dealing with Dependencies 81 Pragmatic Mobility 84 ummar 86 6. System Design and operations 89 Independent Deployability 89 More Servers, More Servers! My Kingdom for a server! 91 Docker and microservices 93 The Role of Service Discovery 94 The Need for an aPi gateway Security Transformation and Orchestration Routing 100 Monitoring and Alerting 101 Summary 101 7. Adopting Microservices in Practice ,,103 Solution architecture guidance 104 How many bug fixes/features should be included in a single release? 104 When do i know our microservice transformation is done? 104 Organizational guidance 105 How do i know if my organization is ready for microservices? 105 Culture guidance 106 How do i introduce change 106 Can i do microservices in a project-centric culture? 108 Can i do microservices with outsourced workers? 108 Tools and process Guidance 109 What kinds of tools and technology are required for microservices? 109 What kinds of practices and processes will I need to support microservices? 110 How do i govern a microservice system? Services guidance 112 Table of contents|ⅶi Should all microservices be coded in the same programming language? 112 What do i do about orphaned components? 113 Summary 113 8. Epilogue. 115 A. Microservice Architecture reading list 117 Index 21 I Table of Contents

试读 127P Microservice-Architecture-Aligning-Principles-Practices-and-Culture.pdf
立即下载 低至0.43元/次 身份认证VIP会员低至7折
    Microservice-Architecture-Aligning-Principles-Practices-and-Culture.pdf 16积分/C币 立即下载

    试读结束, 可继续阅读

    16积分/C币 立即下载 >