In this talk, we will leverage all cloud native stacks and tools to build Camel Quarkus routes natively using GraalVM native-image on Tekton pipeline and deploy these routes to Kubernetes cluster with Knative installed. We will dive into the following topics in the talk: - Introduction to Camel - Introduction to Camel Quarkus - Introduction to GraalVM Native Image - Introduction to Tekon - Introduction to Knative - Demo shows how to deploy end to end a Camel Quarkus route which include the following steps: - Look at whole deployment pipeline for Cloud Native Camel Quarkus routes - Build Camel Quarkus routes with GraalVM native-image on Tekton pipeline. - Deploy Camel Quarkus routes to Kubernetes cluster with Knative Targeted Audience: Users with basic Camel knowledge

1. Build and Deploy Cloud Native
Camel Quarkus Routes With
Tekton and Knative
Omar Al-Safi
APACHECON @HOME
Spt, 29th – Oct. 1st 2020

2. About
Omar Al-Safi
● Open Source Software Engineer at Talend
● Apache Camel PMC and Commiter
● Based in Germany
● Twitter: @omarsmak Github: omarsmak

3. ● What is Cloud Native?
● Introduction to GraalVM Native Image.
● Introduction to Camel Quarkus.
● Introduction to Knative.
● Introduction to Tekton.
● Put it all together with a Demo.
Agenda

4. What is Cloud Native?

5. • Open source stack.
What is Cloud Native?

6. • Open source stack.
• Microservices in containers.
What is Cloud Native?

7. • Open source stack.
• Microservices in containers.
• Dynamically ocheratsted.
What is Cloud Native?

8. • Open source stack.
• Microservices in containers.
• Dynamically ocheratsted.
• Optimized resource utilization.
What is Cloud Native?

9. Introduction To
Native Image

10. What is GraalVM

11. • Java VM based on HotSpot/OpenJDK.
What is GraalVM

12. • Java VM based on HotSpot/OpenJDK.
• High performance runtime.
What is GraalVM

13. • Java VM based on HotSpot/OpenJDK.
• High performance runtime.
• Ahead-of-time (AOT) compilation through Native Image.
What is GraalVM

14. • Java VM based on HotSpot/OpenJDK.
• High performance runtime.
• Ahead-of-time (AOT) compilation through Native Image.
• Ideal for Microservices and Cloud Native applications.
What is GraalVM

15. • Java VM based on HotSpot/OpenJDK.
• High performance runtime.
• Ahead-of-time (AOT) compilation through Native Image.
• Ideal for Microservices and Cloud Native applications.
• Multiple languages interoperability.
What is GraalVM

16. • Java VM based on HotSpot/OpenJDK.
• High performance runtime.
• Ahead-of-time (AOT) compilation through Native Image.
• Ideal for Microservices and Cloud Native applications.
• Multiple languages interoperability.
• Includes as well a Just-in-time (JIT) mode.
What is GraalVM

17. GraalVM Architecture

18. AOT vs JIT
* From: Thomas Wuerthinger performance benchmarks https://twitter.com/thomaswue/status/1145603781108928513

19. GraalVM Native Image Utility
Application
Libraries
JDK
Substrate VM
Point-to Analysis
Run Initializations
Heap Snapshotting
Native
executable
Ahead-of-Time
Compilation
Image Heap
Writing
Input Output

20. Introduction To

21. Java Density Problem
CONTAINER ORCHESTRATION
Node Node Node
Traditional Cloud-Native Java Stack
Traditional Cloud-Native Java Stack
Traditional Cloud-Native Java Stack
Traditional Cloud-Native Java Stack
NodeJS
NodeJS
NodeJS
NodeJS
NodeJS
NodeJS
NodeJS
Go Go Go
Go Go Go
Go Go Go
Go Go Go
Go Go Go
Go Go Go
Go Go Go
* From Apache Camel 3: the next generation of enterprise integration by Claus Ibsen & Andrea Cosentino

22. Java Fast Scaling Problem
* From Apache Camel 3: the next generation of enterprise integration by Claus Ibsen & Andrea Cosentino
SCALE-UP SCALE-DOWN SCALE-TO-
ZERO

23. What is Quarkus

24. • Kubernetes-native full stack Java framework.
What is Quarkus

25. • Kubernetes-native full stack Java framework.
• Container first.
What is Quarkus

26. • Kubernetes-native full stack Java framework.
• Container first.
• Besides OpenJDK HotSpot, utilizes GraalVM Native Image
very efficiently.
What is Quarkus

27. Quarkus Performance

28. What is Camel Quarkus?

29. • A runtime to run Apache Camel components on top of Quarkus.
What is Camel Quarkus?

30. • A runtime to run Apache Camel components on top of Quarkus.
• Utilizes all performance optimizations brought by Quarkus.
What is Camel Quarkus?

31. • A runtime to run Apache Camel components on top of Quarkus.
• Utilizes all performance optimizations brought by Quarkus.
• Allows Camel routes to be compiled natively using GraalVM
Native Image.
What is Camel Quarkus?

32. Performance Comparison
from(timer("foo").period(1000))
.log("Hello World From ApacheCon");

33. Performance Comparison
Camel SpringBoot
Memory used (RSS) ~400MB
Startup time ~ 3s

34. Performance Comparison
Camel SpringBoot
Memory used (RSS) ~400MB
Startup time ~ 3s
Camel Quarkus
Memory used (RSS) ~200MB
Startup time ~ 0.9s

35. Performance Comparison
Camel Quarkus Native
Camel SpringBoot
Memory used (RSS) ~400MB
Startup time ~ 3s
Camel Quarkus
Memory used (RSS) ~200MB
Startup time ~ 0.9s
Memory used (RSS) ~30MB
Startup time ~ 0.3s

36. Introduction To
Knative

37. What is Knative?

38. • A simplified set of tools to manage containers on Kubernetes.
What is Knative?

39. • A simplified set of tools to manage containers on Kubernetes.
• Allows developers to focus on coding.
What is Knative?

40. • A simplified set of tools to manage containers on Kubernetes.
• Allows developers to focus on coding.
• Built as Kubernetes extension with CRD.
• Utilizes Kubernetes goodies.
• Integrates with other non-Knative services.
What is Knative?

41. What is Knative?

42. Eventing
Common events infrastructure
between services
Knative Components
Serving
Deploy your application to K8s

43. Knative Serving
Knative Service
Revision 1 Config ● Deploy app as pod with revision

44. Knative Serving
Knative Service
Revision 1 Config ● Deploy app as pod with revision.
● Network auto-setup.
Route
User

45. Knative Serving
Knative Service
Config ● Deploy app as pod with revision.
● Network auto-setup.
● Revision are scaled up/down
○ Based on load
○ Down to zero
Route
User
Revision 1Revision 1

46. Knative Serving
Knative Service
Config ● Deploy app as pod with revision.
● Network auto-setup.
● Revision are scaled up/down
○ Based on load
○ Down to zero
● Create revisions and auto migrate
Route
User
Revision 1Revision 1
Config
Revision 1Revision 2

47. Knative Serving
Knative Service
Config ● Deploy app as pod with revision.
● Network auto-setup.
● Revision are scaled up/down
○ Based on load
○ Down to zero
● Create revisions and auto migrate
● Traffic splitting
Route
User
Revision 1Revision 1
Config
Revision 1Revision 2
90%
10%

48. Knative Serving
Knative Service
● Deploy app as pod with revision.
● Network auto-setup.
● Revision are scaled up/down
○ Based on load
○ Down to zero
● Create revisions and auto migrate
● Traffic splitting
● Dedicated URLs to Revisions which allows other
uses cases like blue/green deployment.
Route
User
Tester
Route Config
Revision 1Revision 3Tag
* From Stop Calling Knative Serverless! - Doug Davis, IBM
Config
Revision 1Revision 1
Config
Revision 1Revision 2
90%
10%

49. Knative Eventing
Event Source
Event Source
publish
● Event Source is K8s resource producing events as
CloudEvent via HTTP POST.

50. Knative Eventing
Event Source
Event Source
publish
● Event Source is K8s resource producing events as
CloudEvent via HTTP POST.
○ Adapter often used to convert events into
CloudEvents.
Adapter

51. Knative Eventing
Event Source
Broker
Event Source
publish
● Event Source is K8s resource producing events as
CloudEvent via HTTP POST.
○ Adapter often used to convert events into
CloudEvents.
● Broker is central events hub, e.g: Kafka.
Adapter

52. Knative Eventing
Event Source
Broker
Event Source
publish
● Event Source is K8s resource producing events as
CloudEvent via HTTP POST.
○ Adapter often used to convert events into
CloudEvents.
● Broker is central events hub, e.g: Kafka.
● Trigger subscribe events from a Broker.
Adapter Trigger
ingress
Trigger
ingress

53. Knative Eventing
Event Source
Broker
Event Source
publish
● Event Source is K8s resource producing events as
CloudEvent via HTTP POST.
○ Adapter often used to convert events into
CloudEvents.
● Broker is central events hub, e.g: Kafka.
● Trigger subscribe events from a Broker.
○ Filter for specific events.
Adapter Trigger
ingress
Trigger
ingress
filter=
filter=

54. Knative Eventing
Event Source
Broker Trigger Service
Event Source
filter=
publish
subscribe
● Event Source is K8s resource producing events as
CloudEvent via HTTP POST.
○ Adapter often used to convert events into
CloudEvents.
● Broker is central events hub, e.g: Kafka.
● Trigger subscribe events from a Broker.
○ Filter for specific events.
○ Send events to Service as CloudEvent via HTTP POST.
ingress
Adapter
Trigger Service
subscribe
filter=
ingress

55. Introduction To

56. What is Tekton?

57. • A Kubernetes native framework for creating creating
continuous integration and delivery (CI/CD) pipelines.
What is Tekton?

58. • A Kubernetes native framework for creating creating
continuous integration and delivery (CI/CD) pipelines.
• It used to be part of Knative tools.
What is Tekton?

59. • A Kubernetes native framework for creating creating
continuous integration and delivery (CI/CD) pipelines.
• It used to be part of Knative tools.
• Just like Knative, built as Kubernetes extension with Custom
Resource Definition (CRD).
What is Tekton?

60. Tekton Building Blocks
Step
Container
● Step is the smallest block, contains images,
commands, arguments and corresponds to
a K8s container.

61. Tekton Building Blocks
Task
Step
Container
Step
...
● Step is the smallest block, contains images,
commands, arguments and corresponds to
a K8s container.
● Task is a sequence of steps that run in
sequential order and on the same node.
Node

62. Tekton Building Blocks
Pipeline
Task
Step
Container
Step
...
Task
.
.
.
● Step is the smallest block, contains images,
commands, arguments and corresponds to
a K8s container.
● Task is a sequence of steps that run in
sequential order and on the same node.
● Pipeline contains multiple tasks, sequential
or parallel. Executes tasks on different
nodes.
Node
* From Next Generation CI/CD with GKE and Tekton (Cloud Next '19)

63. Put it all together with a
Demo

64. • Camel route with REST component on top of Camel Quarkus
runtime.
• Trigger the Tekton pipeline using an EventListener.
• Build the Camel route natively using GraalVM Native Image in
Tekton using Kaniko.
• Deploy the route from Tekton pipeline as Knative Service.
• The route is accessible through HTTP/GET.
Demo Overview

65. Demo Overview
Pipeline
Build image from
git source
Deploy service to
Knative
EventListener Camel Quarkus
Rest Kn Service
User
HTTP GET /hello?q=
trigger

67. Any Questions ?
Demo project:
https://github.com/omarsmak/camel-talk-examples/tree/master/camel-quarkus-rest