O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Ambassador Fest: "Kubernetes Workflow 101: The Big Picture of Idea to an API in Production"

A codified series of high level steps that we have seen help engineers reach the “aha” moment of understanding how their existing development workflow will need to change when they adopt cloud native technologies like Kubernetes.

  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Ambassador Fest: "Kubernetes Workflow 101: The Big Picture of Idea to an API in Production"

  1. 1. Kubernetes Workflow 101: From an Idea to an API in Production Daniel Bryant
  2. 2. @danielbryantuk Cloud-Native Microservices 2 • Modularisation • Aka “microservices” • Independently: • Build • Release • Scale • Operate
  3. 3. @danielbryantuk3 “You build it, you run it” - Werner Vogels, CTO Amazon i.e. you own what you code, from idea to production
  4. 4. @danielbryantuk Workflow: Full Cycle Development 4 • App teams have full responsibility (and authority) for delivering a service, and ultimately, value to users • Increase agility by accelerating the feedback loop • https://netflixtechblog.com/full-cycle-developers-at-netflix-a08c31f83249
  5. 5. The Kubernetes Migration Journey 5 Exploration Organizational buy-in Cloud-native organization We’re not actually moving faster Let’s release our microservices as a monolith
  6. 6. 6 Safety. The ability to quickly ship changes to production, without fear.
  7. 7. Safety requires multiple strategies 7 Prevention Mitigation Detection Response Most common strategy (e.g., testing). Mitigation, detection, and response are critical strategies for cloud-native organizations when the application is constant flux.
  8. 8. Safety Strategies 8 Prevention Mitigation Detection Response • Testing: integration tests, user acceptance tests, … • High-fidelity replica environments for dev & test • Engineering for resilience • Progressive delivery: canary release, blue/green rollouts, … • Observability • Chaos engineering • Fast dev / test loops • Blameless postmortems • Runbooks & game days • Instant rollback & traceability
  9. 9. Safety needs to be part of your workflow. 9 Develop Test Deploy/ Release Run Progressive Delivery Rollback Observability Chaos Engineering Runbooks Fast dev loop Fast feedback Realistic test environments
  10. 10. 10 Develop Test Deploy/ Release Run Progressive Delivery Rollback Observability Chaos Engineering Runbooks Fast dev loop Fast feedback Realistic test environments
  11. 11. app.getambassador.io thenewstack.io/learning-kubernetes-the-need-for-a-realistic-playground
  12. 12. @danielbryantuk Many thanks! • Learn more: • www.getambassador.io/learn/building-kubernetes-platform • www.getambassador.io/podcasts • www.infoq.com/profile/Daniel-Bryant • Find me in: • Datawire OSS Slack: d6e.co/slack • Twitter @danielbryantuk 12

×