Freedom, responsibility, and dependencies
•Descargar como PPTX, PDF•
3 recomendaciones•590 vistas
This document discusses dependency management challenges that arise as software systems grow in complexity. It presents three classes of solutions: stability solutions like dependency locking that avoid conflicts but do not resolve them; avoidance solutions like building more frequently to reduce conflicts; and modularization solutions like just-in-time shading that isolate dependencies to prevent conflicts. The talk argues that modularization solutions are most effective at handling conflicts, though they are also more intrusive. It highlights Netflix's use of techniques like dependency locking for stability and interest in more modularization approaches going forward.
Recomendados
Más contenido relacionado
Similar a Freedom, responsibility, and dependencies
Similar a Freedom, responsibility, and dependencies (20)
Último
Último (20)
Freedom, responsibility, and dependencies
- 1. Freedom, Responsibility, and Dependencies JON SCHNEIDER Senior Software Engineer – Build Tools at Netflix @jon_k_schneider JFrog SwampUP – May 2015
- 2. Responsible people thrive on freedom and are worthy of freedom
- 3. Why do most companies curtail freedom and become bureaucratic as they grow?
- 4. Desire for Bigger Positive Impact Creates Growth Growth
- 6. Growth Also Often Shrinks Talent Density % High Performance Employees Growth + Complexity
- 7. Chaos Emerges % High Performance Employees Complexity CHAOS
- 8. Process Emerges to Stop the Chaos Process
- 9. Process-focus Drives More Talent Out % High Performance Employees Process
- 10. Then the market shifts…
- 11. The Key: Increase Talent Density Faster Than Complexity Grows
- 12. The Binary Dependency Choice [1] Much like Scala itself, the SBT logo has gone through at least 3 [1]
- 13. Freedom begets responsibility? My freedom The responsibility cost of my freedom to others in my organization “The correct amount of constraint enables creativity more than total freedom does”
- 14. Freedom begets responsibility? My freedom The responsibility cost of my freedom to others in my organization “The correct amount of constraint enables creativity more than total freedom does”
- 15. Build Tools Focus: Nebula REDUCE BOILERPLATE ENRICH ARTIFACT METADATA IDENTIFY PROJECT OWNERS COLLECT BUILD METRICS
- 16. Our gaze has shifted to dependency management
- 20. Skew ocp~1 b~1 b~2 b~3 b~4 c~1 c~2 skew=0 skew=0 skew=0skew=1 skew=3
- 21. Adoption Rate lambda=1 lambda=4 greater lambda = faster adoption
- 23. Astrid Upstreams
- 24. Dependency Insight: Astrid Release Notes Dependency Resolution Upstream Downstream Event Store Read Models
- 25. Version conflict resolution is the hardest problem we face
- 26. The Conflict Resolution Problem app guava:14 guava:14 guava:14 unit tests prove the accuracy of these systems relative to guava 14
- 27. The Conflict Resolution Problem app guava:16 guava:14 upgrade to a later version guava:14
- 28. The Conflict Resolution Problem app guava:16 guava:16 causes evictions guava: 14 guava:16 guava: 14
- 29. The Conflict Resolution Problem app guava:16 guava:16 these code paths need to be tested for correctness guava: 14 guava:16 guava: 14
- 30. Consequences are starting to get serious…
- 31. 3 Classes of Solutions Stability Avoidance Modularization non-intrusive intrusive few many scope of problems solved intrusiveness earlier recent recency as a solution at Netflix
- 32. Stability solutions are stopgap measures that postpone resolving conflict
- 33. Nebula Dependency Locking is our main stability solution
- 34. Dependency Locking 1 2 3 ./gradlew generateLock saveLock ./gradlew test ./gradlew commitLockif tests pass,
- 35. Dependency Locking { "com.google.guava:guava": { "locked": "14.0", "requested": "14.0" }, "org.foo:foo": { "locked": "1.0", "requested": "1.0" } } Extra artifact produced that is later used to add forces on dependencies
- 36. 3 Classes of Solutions Stability Avoidance Modularization non-intrusive intrusive few many intrusiveness earlier recent recency as a solution at Netflix scope of problems solved
- 37. What if everybody built more frequently?
- 38. 3 Classes of Solutions Stability Avoidance Modularization non-intrusive intrusive few many intrusiveness earlier recent recency as a solution at Netflix scope of problems solved
- 39. Modularization
- 41. Revisiting Conflict Resolution app lib1 lib2 guava:16 guava:14 guava:14Unshaded Shaded lib3 guava:14
- 42. Public API Methods app A guava:16 guava:1 4 Unshaded Shaded public Multiset<String> wordCount(String word) public int totalSales(RangeSet<Integer> hourRange) Hard if A has API methods such as