Engineering and Autonomy in the Age of Microservices

B5b0f56c5edce4c54f1fea72e31d8378?s=47 Nic Benders
January 31, 2017

Engineering and Autonomy in the Age of Microservices

B5b0f56c5edce4c54f1fea72e31d8378?s=128

Nic Benders

January 31, 2017
Tweet

Transcript

  1. Engineering & Autonomy
 In the Age of Microservices Nic Benders

    @nicbenders
  2. ©2008-17 New Relic, Inc. All rights reserved. This document and

    the information herein (including any information that may be incorporated by reference) is provided for informational purposes only and should not be construed as an offer, commitment, promise or obligation on behalf of New Relic, Inc. (“New Relic”) to sell securities or deliver any product, material, code, functionality, or other feature. Any information provided hereby is proprietary to New Relic and may not be replicated or disclosed without New Relic’s express written permission. Such information may contain forward-looking statements within the meaning of federal securities laws. Any statement that is not a historical fact or refers to expectations, projections, future plans, objectives, estimates, goals, or other characterizations of future events is a forward-looking statement. These forward-looking statements can often be identified as such because the context of the statement will include words such as “believes,” “anticipates,” “expects” or words of similar import. Actual results may differ materially from those expressed in these forward-looking statements, which speak only as of the date hereof, and are subject to change at any time without notice. Existing and prospective investors, customers and other third parties transacting business with New Relic are cautioned not to place undue reliance on this forward-looking information. The achievement or success of the matters covered by such forward-looking statements are based on New Relic’s current assumptions, expectations, and beliefs and are subject to substantial risks, uncertainties, assumptions, and changes in circumstances that may cause the actual results, performance, or achievements to differ materially from those expressed or implied in any forward-looking statement. Further information on factors that could affect such forward-looking statements is included in the filings we make with the SEC from time to time. Copies of these documents may be obtained by visiting New Relic’s Investor Relations website at ir.newrelic.com or the SEC’s website at www.sec.gov. New Relic assumes no obligation and does not intend to update these forward-looking statements, except as required by law. New Relic makes no warranties, expressed or implied, in this document or otherwise, with respect to the information provided Safe Harbor 2
  3. ©2008-17 New Relic, Inc. All rights reserved. ▪ ▪ ©2008-17

    New Relic, Inc. All rights reserved. 3
  4. ©2008-17 New Relic, Inc. All rights reserved. ©2008-17 New Relic,

    Inc. All rights reserved. 4
  5. ©2008-17 New Relic, Inc. All rights reserved. 5

  6. ©2008-17 New Relic, Inc. All rights reserved. Organizations which design

    systems ... 
 are constrained to produce designs which are copies of the communication structures 
 of these organizations — Mel Conway 6
  7. ©2008-17 New Relic, Inc. All rights reserved. 7

  8. None
  9. ©2008-17 New Relic, Inc. All rights reserved. Organizations which design

    systems ... 
 are constrained to produce designs which are copies of the communication structures 
 of these organizations — Mel Conway 9
  10. ©2008-17 New Relic, Inc. All rights reserved. Organizations which design

    systems ... 
 are constrained to produce designs which are copies of the communication structures 
 of these organizations — Mel Conway 10
  11. ©2008-17 New Relic, Inc. All rights reserved. 11 Characteristics of

    a Microservice Architecture (From https://martinfowler.com/articles/microservices.html) • Componentization via Services • Organized around Business Capabilities • Products not Projects • Smart endpoints and dumb pipes • Decentralized Governance • Decentralized Data Management • Infrastructure Automation • Design for failure • Evolutionary Design
  12. ©2008-17 New Relic, Inc. All rights reserved. 12 Characteristics of

    a Microservice Organization • Componentization via Teams • Organized around Business Capabilities • Products not Projects (Long-Term Ownership) • Smart Teams and dumb (communication) pipes • Decentralized Governance (Teams make decisions) • Decentralized Data Management (Data skills everywhere) • Infrastructure Automation (Self-Serve Infrastructure) • Design for failure • Evolutionary Design
  13. ©2008-17 New Relic, Inc. All rights reserved. 13 Durable, full-ownership

    teams, organized around business capabilities, with the authority to choose their own tasks and the ability to complete those tasks independently. Reduce central control, emphasizing information flow from the center and decision making at the edge. Eliminate dependencies between teams, through org structure changes and tooling improvements.
  14. Let’s have a re-org! ©2008-17 New Relic, Inc. All rights

    reserved. 14
  15. We’re engineers,
 we solve problems,
 let’s solve this one ©2008-17

    New Relic, Inc. All rights reserved. 15
  16. Optimize for agility ©2008-17 New Relic, Inc. All rights reserved.

    16
  17. We hire smart people, let them be smart ©2008-17 New

    Relic, Inc. All rights reserved. 17
  18. We’re data nerds ©2008-17 New Relic, Inc. All rights reserved.

    18
  19. Engineers make
 the decisions Analysis Design Rollout Break dependencies ©2008-17

    New Relic, Inc. All rights reserved. 19
  20. Break dependencies ©2008-17 New Relic, Inc. All rights reserved. 20

  21. ©2008-17 New Relic, Inc. All rights reserved. 21

  22. ©2008-17 New Relic, Inc. All rights reserved. 22

  23. ©2008-17 New Relic, Inc. All rights reserved. 23

  24. ©2008-17 New Relic, Inc. All rights reserved. 24

  25. Make strong teams ©2008-17 New Relic, Inc. All rights reserved.

    25
  26. Full Ownership Teams ©2008-17 New Relic, Inc. All rights reserved.

    26
  27. T-Shaped Engineers ©2008-17 New Relic, Inc. All rights reserved. 27

  28. Invert control ©2008-17 New Relic, Inc. All rights reserved. 28

  29. Self-selection ©2008-17 New Relic, Inc. All rights reserved. 29

  30. Harder than
 it looks :-/ ©2008-17 New Relic, Inc. All

    rights reserved. 30
  31. Managers really didn’t like it :-( ©2008-17 New Relic, Inc.

    All rights reserved. 31
  32. Engineers 
 didn’t like it either :-( ©2008-17 New Relic,

    Inc. All rights reserved. 32
  33. We almost 
 backed down! :-o ©2008-17 New Relic, Inc.

    All rights reserved. 33
  34. Empathize Communicate Rely on your VALUES ©2008-17 New Relic, Inc.

    All rights reserved. 34
  35. The Big Event ©2008-17 New Relic, Inc. All rights reserved.

    35
  36. Self-selection reveals opportunities ©2008-17 New Relic, Inc. All rights reserved.

    36
  37. The power of 
 self determination ©2008-17 New Relic, Inc.

    All rights reserved. 37
  38. Working agreements ©2008-17 New Relic, Inc. All rights reserved. 38

  39. “We work together best when…” ©2008-17 New Relic, Inc. All

    rights reserved. 39
  40. Mob Programming Continuous Deployment Insights Team Weekly Demos & Retros

    ©2008-17 New Relic, Inc. All rights reserved. 40
  41. It really worked! ©2008-17 New Relic, Inc. All rights reserved.

    41
  42. ©2008-17 New Relic, Inc. All rights reserved. 42 Characteristics of

    a Microservice Organization • Componentization via Teams • Organized around Business Capabilities • Products not Projects (Long-Term Ownership) • Smart Teams and dumb (communication) pipes • Decentralized Governance (Teams make decisions) • Decentralized Data Management (Data skills everywhere) • Infrastructure Automation (Self-Serve Infrastructure) • Design for failure • Evolutionary Design
  43. ©2008-17 New Relic, Inc. All rights reserved. Autonomous Teams have

    Rights AND Responsibilities 43 Rights Responsibilities Write your own MMFs Take MMF ideas from others. Keep MMFs “minimal” and focussed on business value. Choose the next MMF to work on Make progress towards Product priorities. Estimate your MMFs Include usability, quality, reliability, scalability, documentation and operability in your estimates. Decide when an MMF is done Meet our Engineering and Product standards. Don’t lose sight of “minimal” or the original business value. Make technology decisions that only affect your team Take new technology decisions seriously. Unexpected problems are still your responsibility. Decide on your own team process Participate in org and company-wide processes. Have a process and follow it.
  44. You hired smart engineers… trust them ©2008-17 New Relic, Inc.

    All rights reserved. 44
  45. Better teams make better products ©2008-17 New Relic, Inc. All

    rights reserved. 45
  46. Jim Shore 46

  47. Liftoff: Launching Agile Teams & Projects Diana Larsen & Ainsley

    Nies Creating Great Teams: How Self-Selection Lets People Excel Sandy Mamoli & David Mole Turn the Ship Around! L. David Marquet The Principles of Product Development Flow Donald G. Reinertsen 47
  48. Thank you. Nic Benders @nicbenders http://nicbenders.com/presentations/microservices-2017/ ©2008-17 New Relic, Inc.

    All rights reserved. 48