Download as PDF, PPTX
Uploaded byMike McGarr
Dependencies, distributed code and engineering velocity
The document discusses challenges faced by engineers at Netflix regarding shared code, versioning, and dependencies in a distributed environment. It outlines the difficulties of managing semantic versions and the complexity of consuming libraries, while also presenting potential solutions like adopting a monorepo approach and distributed refactoring. Ultimately, it aims to address how to improve engineering velocity and reduce consumer pain in software development.
Technologyā¦
More Related Content
Similar to Dependencies, distributed code and engineering velocity
![YTD Video Downloader Pro Crack [Latest 2025]](https://cdn.slidesharecdn.com/ss_thumbnails/distributedapps-250330185247-48b75da1-250407083333-1c55faec-thumbnail.jpg?width=640&height=640&fit=bounds)
Dependencies, distributed code and engineering velocity
- 1. Dependencies, Distributed code and engineeringvelocity Mike McGarr @SonOfGarr Ā© J. Michael McGarr, 2017
- 2. I have aproblem... Ā© J. Michael McGarr, 2017
- 3. ...that impacts everyengineer at Netļ¬ix. Ā© J. Michael McGarr, 2017
- 4. Affects you too. Ā©J. Michael McGarr, 2017
- 5. I don't knowthe solution. Ā© J. Michael McGarr, 2017
- 6. direction Ā© J. MichaelMcGarr, 2017
- 7. So what isthis problem? Ā© J. Michael McGarr, 2017
- 8. SHARED CODEĀ© J. MichaelMcGarr, 2017
- 9. cloud microservices Ā© J.Michael McGarr, 2017
- 10. Ā© J. MichaelMcGarr, 2017
- 11. Ā© J. MichaelMcGarr, 2017
- 12. client libraries Ā© J.Michael McGarr, 2017
- 13. Ā© J. MichaelMcGarr, 2017
- 14. transitive dependencies Ā© J.Michael McGarr, 2017
- 15. Ā© J. MichaelMcGarr, 2017
- 16. consuming libraries should be easyĀ©J. Michael McGarr, 2017
- 17. software isn't static Ā©J. Michael McGarr, 2017
- 18. semantic versions Ā© J.Michael McGarr, 2017
- 19. Ā© J. MichaelMcGarr, 2017
- 20. (*) 3.1.13 3.1.14 3.1.15 3.1.16 3.2.0 3.2.1 3.2.2 3.2.3 4.0.0-RC1 Ā© J.Michael McGarr, 2017
- 21. Which version isgood? Ā© J. Michael McGarr, 2017
- 22. Ā© J. MichaelMcGarr, 2017
- 23. (*) 3.1.13 ā 3.1.14ā 3.1.15 ā 3.1.16 ā 3.2.0 ā 3.2.1 ā 3.2.2 ā 3.2.3 ā 4.0.0-RC1 ā Ā© J. Michael McGarr, 2017
- 24. Ā© J. MichaelMcGarr, 2017
- 25. Semantic versioning isinsufļ¬cient Ā© J. Michael McGarr, 2017
- 26. Ā© J. MichaelMcGarr, 2017
- 27. Ā© J. MichaelMcGarr, 2017
- 28. Which version ofguava will you get? Ā© J. Michael McGarr, 2017
- 29. Ā© J. MichaelMcGarr, 2017
- 30. Ā© J. MichaelMcGarr, 2017
- 31. Pinning versions is technicaldebt Ā© J. Michael McGarr, 2017
- 32. Just give mea version that works!Ā© J. Michael McGarr, 2017
- 33. consuming libraries is actually hardĀ©J. Michael McGarr, 2017
- 34. Well, at least publishing isthe easy, right? Ā© J. Michael McGarr, 2017
- 35. Need to changefoobar-client:3.2.2 ā Bug ļ¬x? 3.2.3 ā Behavior change? 3.2.0 ā API change? 4.0.0 Ā© J. Michael McGarr, 2017
- 36. Who will Ibreak? Ā© J. Michael McGarr, 2017
- 37. Who is consuming mylibrary? Ā© J. Michael McGarr, 2017
- 38. Who is usingthis API that I want to change? Ā© J. Michael McGarr, 2017
- 39. Publishers lack organization-wide visibility Ā© J.Michael McGarr, 2017
- 40. There are solutions out there... Ā©J. Michael McGarr, 2017
- 41. Option #1: Just dealwith pain Ā© J. Michael McGarr, 2017
- 42. Option #2: Share nothing Ā©J. Michael McGarr, 2017
- 43. Option #2: Share nothinglittle Ā© J. Michael McGarr, 2017
- 44. Option #3: Monorepo Ā© J.Michael McGarr, 2017
- 45. ā all codein a single repository ā source integration ā head is production ā no versions ā atomic API changes ā lock step deployments Ā© J. Michael McGarr, 2017
- 46. constraints Ā© J. MichaelMcGarr, 2017
- 47. monorepo depends ongates Ā© J. Michael McGarr, 2017
- 48. Ā© J. MichaelMcGarr, 2017
- 49. Our approach... Ā© J.Michael McGarr, 2017
- 50. Can we getthe beneļ¬ts of a monorepo, without the constraints? Ā© J. Michael McGarr, 2017
- 51. Publisher feedback Managed source Distributedrefactoring Ā© J. Michael McGarr, 2017
- 52. Publisher feedback Ā© J.Michael McGarr, 2017
- 53. Astrid Niagara Ā© J. MichaelMcGarr, 2017
- 54. Ā© J. MichaelMcGarr, 2017
- 55. Ā© J. MichaelMcGarr, 2017
- 56. Ā© J. MichaelMcGarr, 2017
- 57. I now knowwho I will break! Ā© J. Michael McGarr, 2017
- 58. Managed source Ā© J.Michael McGarr, 2017
- 59. eliminate reduce consumer pain Ā©J. Michael McGarr, 2017
- 60. Ā© J. MichaelMcGarr, 2017
- 61. Ā© J. MichaelMcGarr, 2017
- 62. Shorten adoption curve Ā©J. Michael McGarr, 2017
- 63. Give me a versionthat works!Ā© J. Michael McGarr, 2017
- 64. Distributed refactoring Ā© J.Michael McGarr, 2017
- 65. Gradle Lint Ā© J.Michael McGarr, 2017
- 66. How do I Changemy API across hundreds of repos? Ā© J. Michael McGarr, 2017
- 67. 1. Find allrepositories 2. Find all API calls 3. Refactor all API calls 4. Issue pull requests en masse Ā© J. Michael McGarr, 2017
- 68. experimental Ā© J. MichaelMcGarr, 2017
- 69. Publisher feedback Managed source Distributedrefactoring Ā© J. Michael McGarr, 2017
- 70. "Eventually consistent distributedmonorepo" -- Avi Bryant (Stripe) Ā© J. Michael McGarr, 2017
- 71. Will this work? Ā©J. Michael McGarr, 2017
- 72. Thank you Mike McGarr @SonOfGarr mmcgarr@netļ¬ix.com Ā©J. Michael McGarr, 2017