Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to make a technical decision

How to make a technical decision

Anton Davydov

December 19, 2019
Tweet

More Decks by Anton Davydov

Other Decks in Programming

Transcript

  1. View Slide

  2. Hello

    View Slide

  3. My second time here

    View Slide

  4. View Slide

  5. Anton Davydov
    github.com/davydovanton
    twitter.com/anton_davydov
    davydovanton.com

    View Slide

  6. View Slide

  7. View Slide

  8. View Slide

  9. Core member

    View Slide

  10. View Slide

  11. twitch.tv/davydovanton

    View Slide

  12. • OpenSource evangelist
    • Technical consulting

    View Slide

  13. Stickers

    View Slide

  14. • Memes
    • Coffee
    • Beer
    • Kendo
    • Psychology
    • jRPG
    • SW-2039-0208-4228 / 3DS also welcome
    • How to draw images for presentations

    View Slide

  15. View Slide

  16. SOA in toptal

    View Slide

  17. service oriented architecture

    View Slide

  18. Microservices




    View Slide

  19. Very specific and will work
    only in toptal

    View Slide

  20. Why?

    View Slide

  21. We have a specific
    requirements and this
    requirements related only for
    our company

    View Slide

  22. View Slide

  23. View Slide

  24. View Slide

  25. View Slide

  26. Instead make a decision we’re
    trying to find a solution

    View Slide

  27. View Slide

  28. How we made architectural
    decision in toptal

    View Slide

  29. Attention: experimental talk

    View Slide

  30. Zero line of code

    View Slide

  31. Why developers should
    think about it?

    View Slide

  32. 0. personal projects

    View Slide

  33. How to start using own library in
    the company?

    View Slide

  34. 1. “I think it will be good for us”

    View Slide

  35. Works only in small offices

    View Slide

  36. Or with opinion leaders

    View Slide

  37. View Slide

  38. 2. Business wants to understand
    why they need to spend money
    and time for something

    View Slide

  39. View Slide

  40. 3. Sharing knowledge

    View Slide

  41. Private discussions, meetings
    and public channels in slack

    View Slide

  42. Hard to find information without
    knowledge where to find it

    View Slide

  43. 4. Learning and improving code

    View Slide

  44. Loosing context of decision

    View Slide

  45. Decision cycle

    View Slide

  46. problem -> ??? -> solution

    View Slide

  47. problem -> -> solution

    View Slide

  48. View Slide

  49. Problem

    View Slide

  50. Problem
    Requirements

    View Slide

  51. Technology list

    View Slide

  52. View Slide

  53. Technical requirements

    View Slide

  54. Architecture requirements

    View Slide

  55. Business requirements

    View Slide

  56. Current implementation

    View Slide

  57. Problem
    Requirements
    Research solutions

    View Slide

  58. Google

    View Slide

  59. Books

    View Slide

  60. Example: data composition
    approaches

    View Slide

  61. View Slide

  62. Chats

    View Slide

  63. Problem
    Requirements
    Research solutions
    Map solutions to
    requirements

    View Slide

  64. View Slide

  65. PoC

    View Slide

  66. Proof of concept

    View Slide

  67. Expensive

    View Slide

  68. Choose 2 solutions and
    make PoC for them

    View Slide

  69. Problem
    Requirements
    Research solutions
    Map solutions to
    requirements
    Decision

    View Slide

  70. Based on table/PoC/etc

    View Slide

  71. Describe why you dropped
    or choose solution

    View Slide

  72. What to do if solutions
    absolutely equal?

    View Slide

  73. Choose simplest solution

    View Slide

  74. Calculate price

    View Slide

  75. Example: image service

    View Slide

  76. imgix vs imgproxy

    View Slide

  77. Check maintainers

    View Slide

  78. Example

    View Slide

  79. Apache Thrift

    View Slide

  80. Thrift is an interface definition language and binary
    communication protocol used for defining and
    creating services for numerous languages.
    … written in a variety of languages and
    frameworks, including ActionScript, C, C++,[3] C#,
    Cappuccino, Cocoa, Delphi, Erlang, Go, Haskell,
    Java, Node.js, Objective-C, OCaml, Perl, PHP,
    Python, Ruby, Rust, Smalltalk and Swift. ....

    View Slide

  81. View Slide

  82. View Slide

  83. View Slide

  84. PROFIT

    View Slide

  85. Requirements
    Research solutions
    Map solutions to
    requirements
    Decision
    Problem
    Handling results

    View Slide

  86. Can be anything

    View Slide

  87. ADR

    View Slide

  88. Architecture Decision Records

    View Slide

  89. Blog posts

    View Slide

  90. Markdown

    View Slide

  91. Emacs-org

    View Slide

  92. Rules

    View Slide

  93. Context of problem

    View Slide

  94. Who made this decision

    View Slide

  95. Provide pros and cons

    View Slide

  96. Link all research information

    View Slide

  97. # [short title of solved problem and solution]
    * Status:
    * Deciders:
    * Date:
    ## Context and Problem Statement
    ## Decision Drivers
    ## Considered Options
    ## Decision Outcome
    ### Positive Consequences
    ### Negative Consequences
    ## Pros and Cons of the Options
    ## Links

    View Slide

  98. Share results with
    everyone

    View Slide

  99. Example:
    slack
    retro meetings
    weekly updates
    @dev-all in email

    View Slide

  100. Keep all decision in one place

    View Slide

  101. GitHub
    Blog posts
    Confluence space
    Notion space
    Trello

    View Slide

  102. Let’s talk about reality

    View Slide

  103. SOA

    View Slide

  104. SOA is simple

    View Slide

  105. Infrastructure
    * How to deploy apps separately
    * Docker or something else
    * How to share resources
    * cloud or bare metal
    * CI and CD
    * Docker regestry
    * slack bots
    * local k8s cluster

    View Slide

  106. Data
    * data evolution
    * How to store and calculate state
    * Allowed DB
    * How to share data between services

    View Slide

  107. Sync communications
    * frontend <> backend
    * backend <> backend
    * How to handle failed services, DB or integration
    * Distributed tracing
    * Diagram of communications
    * Compatibility level
    * Documentation

    View Slide

  108. Async communication
    * Message bus
    * Message schema evolution
    * Schema registry
    * How to consume and produce data
    * Distributed tracing
    * Diagram of communications
    * Compatibility level
    * Documentation

    View Slide

  109. Gateways
    * api gateway
    * GQL gateway (if needed)
    * schema stitching
    * JSON API to GQL

    View Slide

  110. Business logic and domains
    * distributed transactions
    * distributed locks
    * DDD and domain sharing
    * business events
    * microservice chassis

    View Slide

  111. Management,
    teams and processes

    View Slide

  112. Testing
    * contract testing
    * chaos engenering
    * e2e testing

    View Slide

  113. Local development

    View Slide

  114. AuthN / AuthZ

    View Slide

  115. Observability
    * App level
    * Logs
    * Metrics
    * Error handling
    * Company level
    * Services diagram
    * Service characteristics
    * Service owning

    View Slide

  116. Analytics
    * ETL
    * How to get data from services
    * Event based approach
    * How to work with DS models?

    View Slide

  117. And more

    View Slide

  118. Example from real live

    View Slide

  119. Sync communications
    * frontend <> backend
    * backend <> backend
    * How to handle failed services, DB or integration
    * Distributed tracing
    * Diagram of communications
    * Compatibility level
    * Documentation

    View Slide

  120. Sync communications
    * frontend <> backend
    * backend <> backend
    * How to handle failed services, DB or integration
    * Distributed tracing
    * Diagram of communications
    * Compatibility level
    * Documentation

    View Slide

  121. Step 1

    View Slide

  122. Requirements
    Research solutions
    Map solutions to
    requirements
    Decision
    Problem
    Handling results

    View Slide

  123. Avoid proliferation of solutions
    for sync communication in the
    future as the number of
    services keeps growing.

    View Slide

  124. Step 2

    View Slide

  125. Requirements
    Research solutions
    Map solutions to
    requirements
    Decision
    Problem
    Handling results

    View Slide

  126. • Uses JSON for serialization
    • Works with HTTP/1.1
    • IDL + Tolerant reader
    • Bulshitless discussions
    • Pact integration
    • Simple documentation
    • Works with ruby, node.js, go, elixir, java
    • Easy for debugging

    View Slide

  127. Step 3

    View Slide

  128. Requirements
    Research solutions
    Map solutions to
    requirements
    Decision
    Problem
    Handling results

    View Slide

  129. Google

    View Slide

  130. • JSON API
    • JSON RPC
    • gRPC
    • avroRPC
    • thriftRPC
    • GraphQL

    View Slide

  131. Other experience

    View Slide

  132. • Shopify - GQL
    • Github - BERT-RPC and GQL
    • Gitlab - nothing
    • Airbnb - Thrift
    • Heroku - JSON API
    • Coinbase - gRPC
    • Cookpad - gRPC
    • Twitter - Thrift

    View Slide

  133. Interesting use cases

    View Slide

  134. Twitch

    View Slide

  135. Twirp

    View Slide

  136. gRPC over HTTP/1.1

    View Slide

  137. JSON serialisation

    View Slide

  138. Netflix

    View Slide

  139. View Slide

  140. Step 4

    View Slide

  141. Requirements
    Research solutions
    Map solutions to
    requirements
    Decision
    Problem
    Handling results

    View Slide

  142. View Slide

  143. PoC

    View Slide

  144. View Slide

  145. Step 5

    View Slide

  146. Requirements
    Research solutions
    Map solutions to
    requirements
    Decision
    Problem
    Handling results

    View Slide

  147. View Slide

  148. View Slide

  149. We made notes about all
    dropped solution

    View Slide

  150. View Slide

  151. Step 6

    View Slide

  152. Requirements
    Research solutions
    Map solutions to
    requirements
    Decision
    Problem
    Handling results

    View Slide

  153. Blog post

    View Slide

  154. View Slide

  155. All meetings notes

    View Slide

  156. View Slide

  157. View Slide

  158. View Slide

  159. Researched information + PoC
    examples for the team who will
    implement communications

    View Slide

  160. Current state

    View Slide

  161. Everyone from toptal can
    read how and why we
    made this research

    View Slide

  162. View Slide

  163. I used all this information for
    the presentation’s example

    View Slide

  164. Requirements
    Research solutions
    Map solutions to
    requirements
    Decision
    Problem
    Handling results

    View Slide

  165. Next steps

    View Slide

  166. Share research with
    everyone

    View Slide

  167. Start writing context of
    each decision

    View Slide

  168. # [short title of solved problem and solution]
    * Status:
    * Deciders:
    * Date:
    ## Context and Problem Statement
    ## Decision Drivers
    ## Considered Options
    ## Decision Outcome
    ### Positive Consequences
    ### Negative Consequences
    ## Pros and Cons of the Options
    ## Links

    View Slide

  169. # [short title of solved problem and solution]
    * Status:
    * Deciders:
    * Date:
    ## Context and Problem Statement
    ## Decision Drivers
    ## Considered Options
    ## Decision Outcome
    ### Positive Consequences
    ### Negative Consequences
    ## Pros and Cons of the Options
    ## Links

    View Slide

  170. Make special place for
    decisions

    View Slide

  171. Try to use ADRs if you
    don’t want to spend much
    time for researching

    View Slide

  172. Share your progress with
    colleagues and start
    discussion

    View Slide

  173. Thank you ❤
    twitter.com/anton_davydov
    github.com/davydovanton
    [email protected]
    davydovanton.com

    View Slide