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.

Intro to Knative

1.670 visualizações

Publicada em

A quick look through Knative and serverless

Publicada em: Software
  • Seja o primeiro a comentar

Intro to Knative

  1. 1. What is Knative? @christianposta
  2. 2. Christian Posta Chief Architect, cloud application development Twitter: @christianposta Blog: http://blog.christianposta.com Slides: http://slideshare.net/ceposta • Author “Microservices for Java developers” and “Introducing Istio Service Mesh” • Committer/contributor lots of open-source projects • Blogger, speaker, mentor, leader
  3. 3. Kubernetes Established primitives for deploying and managing container workloads at scale
  4. 4. Istio How workloads interact with each other over the network in a secure, reliable, observable way
  5. 5. Knative “PaaS” like abstractions on top of Kubernetes that leverage Istio and raise the level of abstraction for specifying, running, and modifying applications
  6. 6. Is Knative “Severless”?
  7. 7. Well… WTF is “serverless”? @christianposta
  8. 8. @christianposta Serverless: outsourcing core infrastructure services to cloud providers and stitching it all together through APIs (and functions) to deliver business value
  9. 9. Service Full? https://www.slideshare.net/jedi4ever/from-serverless-to-service-full-how-the-role-of-devops-is-evolving
  10. 10. ● Per-request billing / pay as you go ● Typically accessed via APIs ● You don’t own it or care how it’s implemented ● Agreed SLAs ● Explicit choice, with tradeoffs, to not own the technology to run your business Service-full
  11. 11. ● New, smaller unit of compute ● Executed on demand, typically in response to events ● Used to glue together APIs, services ● Concurrency, scale, spin up/spin down, etc done by platform ● High utilization rates (wrt billing – pay for what you use) Functions (FaaS)
  12. 12. ● Agility ● Flexibility (opinionatedness) ● Cost/utilization ● Technology ownership ● Complexity Tradeoffs across these (at least spectrums):
  13. 13. When to use Serverless, Functions, Microservices, Monoliths? @christianposta ^^^ Save this for after 
  14. 14. Back to Knative… @christianposta
  15. 15. Knative is building blocks for a PaaS @christianposta
  16. 16. Knative operates on containers. Those containers can be anything. Can they be functions? Can you build FaaS on Knative? @christianposta
  17. 17. Let’s take a look at one of the “building blocks”… @christianposta
  18. 18. Let’s take a look at these building blocks @christianposta
  19. 19. Knative Serving: Allow our compute utilization to be driven by request load (think: autoscaler) and scale to zero when no load
  20. 20. Knative Eventing: Composing services and compute resources via events to build staged event driven architectures
  21. 21. Knative Build: Converting source packages into runnable containers
  22. 22. Knative Pipelines: Leverage Knative Build and Knative Events to abstract away CI/CD implementations on top of Kubernetes
  23. 23. Knative Caching: Simple API for providing caching to Knative components (TBD - still being sorted out).
  24. 24. Those most mature of the building blocks is Knative serving @christianposta
  25. 25. @christianposta
  26. 26. @christianposta
  27. 27. @christianposta
  28. 28. @christianposta
  29. 29. Thanks! BTW: Hand drawn diagrams made with Paper by FiftyThree.com  Twitter: @christianposta Blog: http://blog.christianposta.com Email: christian@redhat.com Slides: http://slideshare.net/cepostaFollow up links: • http://blog.christianposta.com • http://istio.io • http://envoyproxy.io • http://linkerd.io • http://consul.io • http://bit.ly/istio-tutorial • http://blog.christianposta.com/istio-workshop/slides/