Skip to main content

Spinnaker is a “Standard Library” for Cloud-Native Software Delivery

We just did a great panel with Alan Shimmel of DevOps.com, along with:

  • Sarah Novotny, Open Source in Microsoft’s Azure Office of the CTO
  • Kelsey Hightower, Staff Developer Advocate at Google
  • Andy Glover, Director of Productivity Engineering at Netflix
  • Isaac Mosquera, CTO at Armory and DROdio, CEO at Armory

Kelsey described Spinnaker as a “Standard Library” for software delivery, instead of piecing together software delivery tooling yourself.

In the video we discuss:

  • Minute 2:35: Leaders in the Spinnaker community from Netflix, Microsoft and Google, talking about thems around enterprise software delivery
  • Minute 4:15: How enterprises are moving beyond the Spinnaker use-case, and the investments IaaS providers are making in the cloud
  • Minute 5:55: Discovery’s use case example — an ability to deploy with safety and security to multiple cloud targets
  • Minute 8:01: Being able to deploy code “when it’s ready” — if it’s ready in 6 months, being able to deploy in “6 months and two minutes”
  • Minute 9:18: Delivery is just one of many steps in software delivery
  • Minute 10:20: How long does it take to create a platform like Spinnaker?
  • Minute 12:45: How “tall do you need to be to ride the ride?” Discussing levels of sophistication to leverage the value from a project like Spinnaker
  • Minute 15:03: How Spinnaker is a platform that enables companies to get both safety and velocity — and prioritize developer value creation potential
  • Minute 16:20: How Spinnaker enables trust within an organization to achieve not just continuous delivery, but continuous improvement
  • Minute 19:30: What companies are and are not a good fit for Spinnaker
  • Minute 21:40: How “8 apps” is a tipping point
  • Minute 22:18: How Spinnaker acts as a “Standard Library” for software delivery, instead of piecing together software delivery tooling yourself
  • Minute 26:20: Sharing best-practices across all users by using Spinnaker, due to its OSS and modular plug-in nature
  • Minute 29:40: The “Spinnaker and” approach vs. “Spinnaker or”.
  • Minute 31:10: How to leverage the opinionated nature of Spinnaker while leveraging it as a set of core building blocks:  — for example, “blue/green” deployments can mean something different across teams and companies
  • Minute 38:30: Spinnaker is OSS — focus your effort on helping make it better, instead of re-building your tooling in-house
  • Minute 41:05: Focus on the bigger picture — throwing the birthday party vs. baking the cake