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

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

Oct 22, 2020 by DROdio

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
Share this post:

Recently Published Posts

Argo + Armory: Cross-environment orchestration made easy

Feb 1, 2023

Cross-environment orchestration that you don’t have to spend time building At Armory, our goal is software innovation, whether that’s our own Continuous Deployment solutions, or being able to help our customers reach higher innovation peaks within their software development. We’ve taken deliberate steps to make sure our products play well with others, with a focus […]

Read more

Navigating AWS Deployment Targets with Armory

Jan 20, 2023

Many organizations look to Amazon Web Services (AWS) to host and deploy their applications in the cloud. However, they’re finding that their deployment tooling, often built as an extension of their legacy continuous integration (CI), is one of the main impediments to adopting cloud services.  Custom-scripted production pipelines built with in-house tooling need to be […]

Read more

Release Roundup – January 2023

Jan 11, 2023

Get the latest product news on Continuous Deployment-as-a-Service and the most recent release for Continuous Deployment Self Hosted, 2.28.2. Welcome to 2023!  Just like every organization, Armory is looking for ways to improve our practices and deliver more value (and faster!) to you, our customers. That’s why our engineering team is working to deliver features, […]

Read more