Daniel Oh - Serverless Functions - New Approach to DevApps from Quarkus to Helm
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
COVID-19 causes new issues on how we keep saving infrastructure costs and optimize resource utilization across the industries.
DevOps platform on Kubernetes should be a great solution to address critical issues from the Ops perspective. In the meantime, application workloads are also transferring to serverless functions with event-driven architecture.
The question is what tools & frameworks are capable of dealing with the new approach to DevApps because the Serverless Functions are all the matter as long as you want faster response time, portable development, deployable services in multiple serverless platforms.
In this session, we will walk you through the way developers create a serverless function by triggering over HTTP requests and CloudEvents using multiple cloud-native runtimes(i.e. Quarkus, Go, Spring Boot, Nodejs) on Knative with Kubernetes.
For example, how effectively Quarkus allows you to write portable functions from scratch using knative function CLI but also modernize a traditional microservices project using Funqy extension.
In production, you will also learn how to manage cloud-native applications using Helm chart on Kubernetes from more Ops perspective.
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.