Skip to content

Instantly share code, notes, and snippets.

@jkschneider
Created April 8, 2018 14:05
Show Gist options
  • Save jkschneider/a30ffc9f249a08e003f8cb3271dae7f4 to your computer and use it in GitHub Desktop.
Save jkschneider/a30ffc9f249a08e003f8cb3271dae7f4 to your computer and use it in GitHub Desktop.
Repave and repair talk

Repave and repair your applications with confidence

If a security vulnerability is reported in a common java library today, would you be able to identify affected applications and repair your whole organization before dinner time?

In this talk, we're going to stitch together a continuous delivery platform, application monitoring, automated canary analysis, and organization-wide code search to show you how you can identify affected applications in minutes and repair your organization's code. We'll start with the assumption that we are working with a complex multi-platform (some K8S, some GCP, multiple Cloud Foundry foundations over private VSphere) environment like those found in many organizations.

Some of the tools we'll demonstrate include Spinnaker for continuous delivery, Kayenta for automated canary analysis, Micrometer for metrics collection, Prometheus for monitoring, and Rewrite for code search.

Bio

Jon is a Principal Software Engineer at Pivotal, working on the Spring team on application monitoring and continuous delivery. Previously, he worked at Netflix on developer productivity tools related to distributed refactoring, dependency insight, and build tools. Jon is a St. Louis native but currently resides in Prairie Home, MO with his wife and three kids.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment