6. Knative
“PaaS” like abstractions on top of Kubernetes that
leverage Istio and raise the level of abstraction for
specifying, running, and modifying applications
12. ● 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
13. ● 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)
14. ● Agility
● Flexibility (opinionatedness)
● Cost/utilization
● Technology ownership
● Complexity
Tradeoffs across these (at least spectrums):
15. When to use Serverless, Functions,
Microservices, Monoliths?
@christianposta
^^^ Save this for after
34. 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/
Notes de l'éditeur
How many people are embarking on projects to drive innovation in their organizations?
How many people think those projects will succeed?
How many people can predict the future?
How many people believe their organization’s executives can predict the future?