Openshift Serverless - Sicpa

Transcript

1. Openshift Serverless using Knative and Quarkus
2. Kevin Dubois • Developer Advocate at Red Hat • 18+ years of experience writing and delivering software • Speak English, Dutch, French, Italian • Passionate about improving Dev Experience with Open Source @kevindubois@mastodon.social youtube.com/@thekevindubois linkedin.com/in/kevindubois github.com/kdubois @kevindubois.com Magali David-Cruz • Solution Architect at Red Hat • Your local contact @Red Hat • Speak English, French • DevOps, Kubernetes, Open Source magali@redhat.com
3. Why Serverless?
4. Serverless “Serverless computing refers to the concept of building and running applications that do not require server management. It describes a finer-grained deployment model where applications, bundled as one or more functions are uploaded to a platform and then executed, scaled, and billed in response to the exact demand needed at the moment” -- CNCF Definition, https://www.cncf.io/blog/2018/02/14/cncf-takes-first-step-towards-serverless-computing/
5. Serverless Over provisioning Time in capacity planning IT cost of idle resources Under provisioning Lost business revenue Poor quality of service More applications Direct line between IT costs & business revenue NOT Serverless with Serverless
6. Knative https://github.com/knative
7. Serverless == FaaS?
8. AWS Lambda, Functions... Built around the FaaS components and other services such as API Gateways. It enabled a variety of use cases but it is far from ideal for general computing and with room for improvements. 1.0 ➔ HTTP and other few Sources ➔ Functions only ➔ Limited execution time (5 min) ➔ No orchestration ➔ Limited local development experience Serverless Containers With the advent of containers & Kubernetes, many frameworks and solutions started to auto-scale containers. Cloud providers created offerings using managed services completely abstracting Kubernetes APIs. 1.5 ➔ Fargate, Cloud Run, Container Instances ➔ Knative, KEDA, etc ➔ Kubernetes based auto-scaling ➔ Microservices and Functions ➔ Easier to debug & test locally ➔ Polyglot & Portable Integration & State The maturity and benefits of Serverless are recognized industry wide and it adds the missing parts to make pattern suitable for general purpose workloads and used on the enterprise. 2.0 ➔ Basic state handling ➔ Enterprise Integration Patterns ➔ Advanced Messaging Capabilities ➔ Blended with your PaaS ➔ Enterprise-ready event sources ➔ Solutions and outcome focused
9. Immutable revisions Deploy new features: performing canary, A/B or blue-green testing with gradual traffic rollout with no sweat and following best practices. No need to configure number of replicas, or idling. Scale to zero when not in use, auto scale to thousands during peak, with built-in reliability and fault-tolerance. Automatic scaling Ready for the Hybrid Cloud Truly portable serverless running anywhere OpenShift runs, that is on-premises or on any public cloud. Leverage data locality and SaaS when needed. Event Driven Architectures Build loosely coupled & distributed apps connecting with a variety of built-in or third-party event sources or connectors powered by Operators. Any programming language Use any programming language or runtime of choice. From Java, Python, Go and JavaScript to Quarkus, SpringBoot or Node.js. Simplified developer experience to deploy applications/code on serverless containers abstracting infrastructure & focusing on what matters. Containers made easy prem aws azure OpenShift Serverless Knative with batteries included
10. Demo
11. $ kn func create -l quarkus myfunc $ kn func deploy $ quarkus create app -x funqy-knative-cloud-event $ kn service create myservice --image=xyz
12. Demo
15. OpenShift Sandbox: We changed the default deployment type to Serverless
17. Knative Eventing Eventing is a set of APIs for routing events from Producers to Consumers (known as Sinks) CloudEvent specification allows for the creation of Serverless components that are driven by Event rather than Traffic
18. CloudEvents CNCF incubating project - https://cloudevents.io/ Provides a common event schema => Interoperability, portability Extensible through extension attributes SDKs for different programming languages Protocol-agnostic (HTTP, AMQP, MQTT, …) Wide adoption
19. Usage Patterns Source to Sink
20. Usage Patterns Channel and Subscription
21. Usage Patterns Broker and Trigger
22. Java?
23. Serverless Adoption 6.1% Java https://serverless.com/blog/2018-serverless-community-survey-huge-growth-usage/ 62.9% Node.js 20.8% Python 6.4% Go 6.1% Java 3.8% C#
24. https://greenlab.di.uminho.pt/wp-content/uploads/2017/10/sleFinal.pdf Energy Efficiency across Programming Languages
25. JVM Scaling
26. When you can’t scale fast enough…
27. Build Time Runtime @ @ </> Traditional Java vs Quarkus Runtime Build Time @ @ </> Package model Build Time Runtime @ @ </>
28. Supersonic Subatomic Java Quarkus + Native (via GraalVM) 12 MB Quarkus + JVM (via OpenJDK) 73 MB Traditional Cloud-Native Stack 136 MB Quarkus + Native (via GraalVM) 0.016 Seconds Quarkus + JVM (via OpenJDK) 0.943 Seconds Traditional Cloud-Native Stack 4.3 Seconds
29. • OpenShift serverless enables serverless on hybrid cloud environments • Serverless can help to save resources and increase cluster density • Knative can turn regular containers easily into serverless • Quarkus makes Java applications serverless ready • Build event-driven and FaaS applications with Knative Takeaways
30. Free Developer e-Books! developers.redhat.com/e-books
31. Start exploring in the OpenShift Sandbox. Learn containers, Kubernetes, and OpenShift in your browser. developers.redhat.com/developer-sandbox Try Red Hat's products and technologies without setup or configuration.
32. github.com/kdubois/quarkus-knative-func
33. github.com/kdubois/CamelQuarkusVoter redhat-developer-demos.github.io/knative-tutorial
34. Thank you! @kevindubois@mastodon.social youtube.com/@thekevindubois linkedin.com/in/kevindubois github.com/kdubois @kevindubois.com