Skip to content

Commit 1fb16f6

Browse files
committed
add Charlotte JUG talk
1 parent 7deb43f commit 1fb16f6

File tree

3 files changed

+18
-1
lines changed

3 files changed

+18
-1
lines changed

_data/navigation.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,3 +17,4 @@
1717
- gradle_summit_2015_dthomas
1818
- gradle_summit_2015_rspieldenner
1919
- jconfmexico2020_robertoperezalcolea
20+
- charlotte_jug_2021_robertoperezalcolea
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
layout: video-page
3+
title: Dependency Management at Scale
4+
id: charlotte_jug_2021_robertoperezalcolea
5+
youtube_id: "kCKjrWDMSg"
6+
---
7+
8+
## Dependency Management at Scale (Roberto Perez Alcolea)
9+
10+
In an environment where software is constantly changing and new versions of a library should be distributed across thousands of projects, how can you know that your projects are using the right version of a given dependency? What if a OSS library introduces a security vulnerability and you need to make sure that no one is using it in your company? What if an internal library introduces a bad change and you need everyone to upgrade/downgrade? Automating these for hundreds or thousands of engineers is crucial.
11+
12+
At Netflix, engineers are not immune to the cost of dependency updates. Library owners publish new versions of their code without a comprehensive understanding of the organizational impact. Application owners ingest new library versions that can fail in obvious or subtle ways, leading to decreased confidence and slower organizational velocity. But these are problems we understand, and tooling can help.
13+
14+
After years of evolving our build, we've developed a few conceptual models of dependency management. Dependency management is hard, and in all cases there are compromises, and you the build owner should be conscious of which choices you're making and what else is available.
15+
16+
On this session, we'll introduce some tools we've developed at Netflix which attack dependency issues on a large scale to make it easier for every JVM engineer at Netflix and how we react to the scenarios mentioned above.

videos/jconfmexico2020_robertoperezalcolea.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
layout: video-page
3-
title: Dependency Management at Scale
3+
title: Dependency Management at Scale (Spanish)
44
id: jconfmexico2020_robertoperezalcolea
55
youtube_id: "DykdvD6MTZY"
66
---

0 commit comments

Comments
 (0)