From 87980483e15053801de196c0c9ee812dbdda898b Mon Sep 17 00:00:00 2001 From: lburgazzoli Date: Thu, 1 Feb 2024 13:08:25 +0000 Subject: [PATCH] deploy: e3813001d5a343a125ce361429aca0a0b4a5df98 --- 404.html | 11 ++++++++--- about/index.html | 11 ++++++++--- categories/index.html | 11 ++++++++--- index.html | 11 ++++++++--- index.xml | 2 +- .../index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../2018-07-29-polyglot-camel-routes/index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../index.html | 11 ++++++++--- .../index.html | 17 +++++++++++------ posts/index.html | 11 ++++++++--- posts/index.xml | 2 +- tags/camel/index.html | 11 ++++++++--- tags/camel/index.xml | 2 +- tags/cloud/index.html | 11 ++++++++--- tags/clustering/index.html | 11 ++++++++--- tags/fabric8/index.html | 11 ++++++++--- tags/functions/index.html | 11 ++++++++--- tags/graalvm/index.html | 11 ++++++++--- tags/index.html | 11 ++++++++--- tags/java8/index.html | 11 ++++++++--- tags/karaf/index.html | 11 ++++++++--- tags/kubernetes/index.html | 11 ++++++++--- tags/lowcode/index.html | 11 ++++++++--- tags/microservices/index.html | 11 ++++++++--- tags/openshift/index.html | 11 ++++++++--- tags/pulsar/index.html | 11 ++++++++--- tags/scripting/index.html | 11 ++++++++--- tags/spring-boot/index.html | 11 ++++++++--- tags/spring-cloud/index.html | 11 ++++++++--- tags/wasm/index.html | 11 ++++++++--- tags/wasm/index.xml | 2 +- 39 files changed, 287 insertions(+), 112 deletions(-) diff --git a/404.html b/404.html index 5393568..ef554db 100644 --- a/404.html +++ b/404.html @@ -7,6 +7,11 @@ Ideas are my own. ">

404 NOT FOUND

You just hit a route that doesn't exist.

\ No newline at end of file + ">

404 NOT FOUND

You just hit a route that doesn't exist.

+ \ No newline at end of file diff --git a/about/index.html b/about/index.html index d2544df..8443d86 100644 --- a/about/index.html +++ b/about/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

  • Senior Principal Software Engineer and architect at Red Hat
  • Committer and PMC member on Apache Camel
  • co-creator of Apache Camel K, a lightweight platform for running Apache Camel integrations on Kubernetes that leverages Knative for “serverless” features.
\ No newline at end of file + ">

  • Senior Principal Software Engineer and architect at Red Hat
  • Committer and PMC member on Apache Camel
  • co-creator of Apache Camel K, a lightweight platform for running Apache Camel integrations on Kubernetes that leverages Knative for “serverless” features.
+ \ No newline at end of file diff --git a/categories/index.html b/categories/index.html index c990ca4..fffba6a 100644 --- a/categories/index.html +++ b/categories/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

Categories

\ No newline at end of file + ">

Categories

+ \ No newline at end of file diff --git a/index.html b/index.html index 57d8112..a2c85ec 100644 --- a/index.html +++ b/index.html @@ -7,7 +7,12 @@ Ideas are my own. ">

Recent Posts

See all posts

+ \ No newline at end of file diff --git a/index.xml b/index.xml index f36f9e0..208fdc6 100644 --- a/index.xml +++ b/index.xml @@ -1,4 +1,4 @@ -Luca Burgazzolihttps://lburgazzoli.github.io/Recent content on Luca BurgazzoliHugo -- gohugo.ioen-usSun, 14 Jan 2024 00:00:00 +0000Apache Camel meets WASM - Part 1https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/Sun, 14 Jan 2024 00:00:00 +0000https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them. +Luca Burgazzolihttps://lburgazzoli.github.io/Recent content on Luca BurgazzoliHugo -- gohugo.ioen-usSun, 14 Jan 2024 00:00:00 +0000Apache Camel meets Wasm - Part 1https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/Sun, 14 Jan 2024 00:00:00 +0000https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them. Background To get started, let’s have a basic understanding of the components/technologies we are going to mention in this post: Apache Camel is an open-source integration framework that provides a set of tools and patterns for facilitating the integration of various applications, systems, and technologies.Apache Camel Pulsar Function, Part 1https://lburgazzoli.github.io/posts/2023-06-13-apache-camel-pulsar-function-pt_1/Thu, 15 Jun 2023 00:00:00 +0000https://lburgazzoli.github.io/posts/2023-06-13-apache-camel-pulsar-function-pt_1/I recently came across an interesting article from DataStax about simplified, low-code friendly data piepelines with Pulsar Function and since I always wanted to learn a little bit more about Apache Pulsar and I’ve been working on something similar, I’ve started exploring how a Pulsar Function based on Apache Camel would look like. Background To get started, let’s have a basic understanding of Apache Pulsar and Apache Camel: diff --git a/posts/2016-10-24-def-svc-fabric8applykarafand-thencamel/index.html b/posts/2016-10-24-def-svc-fabric8applykarafand-thencamel/index.html index 7b7487e..6e5cf56 100644 --- a/posts/2016-10-24-def-svc-fabric8applykarafand-thencamel/index.html +++ b/posts/2016-10-24-def-svc-fabric8applykarafand-thencamel/index.html @@ -7,7 +7,8 @@ Ideas are my own. "> \ No newline at end of file +[INFO] F8: 2016-10-24 15:50:22,419 | INFO | #2 - timer://foo | timer | 36 - org.apache.camel.camel-core - 2.18.0 | Body is: Hello from Minishift, DataCenter is: dc1 + \ No newline at end of file diff --git a/posts/2016-10-27-fromjava7anonymous-classestojava8lambda/index.html b/posts/2016-10-27-fromjava7anonymous-classestojava8lambda/index.html index ff2c916..86be043 100644 --- a/posts/2016-10-27-fromjava7anonymous-classestojava8lambda/index.html +++ b/posts/2016-10-27-fromjava7anonymous-classestojava8lambda/index.html @@ -7,7 +7,8 @@ Ideas are my own. "> \ No newline at end of file + .end(); + \ No newline at end of file diff --git a/posts/2016-12-21-a-camel-running-in-the-clouds/index.html b/posts/2016-12-21-a-camel-running-in-the-clouds/index.html index bb203a7..775db8a 100644 --- a/posts/2016-12-21-a-camel-running-in-the-clouds/index.html +++ b/posts/2016-12-21-a-camel-running-in-the-clouds/index.html @@ -7,7 +7,8 @@ Ideas are my own. ">

  1. Web Service invoked on POD camel-cloud-svc-1-sbkbi

  2. Web Service invoked on POD camel-cloud-svc-1-ojyy6

Wrap up

What’s happen under the hood ?

  1. Spring Cloud Kubernetes automatically creates a DiscoveryClient which is used to lookup services by name

  2. Spring Cloud Commons/Netflix automatically creates a LoadBalancerClient which leverages Netflix’s Ribbon for load balancing

  3. Camel Spring Cloud automatically configure the SerivceCall EIP to use the LoadBalancerClient created by Spring Cloud

Warning
This is a work in progress so things may change in the next future.
+ \ No newline at end of file diff --git a/posts/2017-04-12-a-camel-running-in-the-clouds-part-2/index.html b/posts/2017-04-12-a-camel-running-in-the-clouds-part-2/index.html index 2fee59a..307b0a9 100644 --- a/posts/2017-04-12-a-camel-running-in-the-clouds-part-2/index.html +++ b/posts/2017-04-12-a-camel-running-in-the-clouds-part-2/index.html @@ -7,7 +7,8 @@ Ideas are my own. ">

That’s all!

Under the hood the camel starter perform auto configuration of the underlying services such as:

  • A LoadBalancer based on NetflixOSS Ribbon

  • A ServiceDiscovery based on HashiCorp Consul

  • A ServiceFilter based on Consul’s service health

If needed you can add additional Service Discovery to the mix and under the hood camel will bridge them i.e. you can add a static list of services to the mix with a simple configuration like:

application.properties
camel.cloud.service-discovery.services[myService] = host1:8080,host2:8080,host3:8080
Tip
You can use Spring Cloud and Spring Cloud Netflix instead of Camel’s own consul/ribbon implementation by using camel-spring-cloud-starter and camel-spring-cloud-netflix-starter.

Ready to use Implementations

Camel provides some implementations of the conceept we have introduced sat the biginning of the post out of the box:

TypeNameArtifact

Service Discovery

Static service discovery

camel-core

Chained service discovery

camel-core

Consul based service discovery

camel-consul

DNS SRV based service discovery

camel-dns

Etcd based service discovery

camel-etcd

Kubernetes based service discovery

camel-kubernetes

Service Filter

Healty filter

camel-core

Pass through filter

camel-root

Blacklist service filter

camel-core

Chained service filter

camel-core

Service Chooser

Round robin chooser

camel-core

Random chooser

camel-core

Load Balancer

Default load balancer

camel-core

SpringCloud load-balancer

camel-spring-cloud

+ \ No newline at end of file diff --git a/posts/2017-10-13-a-camel-running-in-the-clouds-part-3/index.html b/posts/2017-10-13-a-camel-running-in-the-clouds-part-3/index.html index eeef59f..9ad1583 100644 --- a/posts/2017-10-13-a-camel-running-in-the-clouds-part-3/index.html +++ b/posts/2017-10-13-a-camel-running-in-the-clouds-part-3/index.html @@ -7,7 +7,8 @@ Ideas are my own. ">
Important

Health Checks are an experimental feature which will be improved in the next Camel releases.

1. Azure Health Endpoint pattern
2. Consul Health Checks
+ \ No newline at end of file diff --git a/posts/2017-10-21-apache-camel-features-spotlight-cluster-service/index.html b/posts/2017-10-21-apache-camel-features-spotlight-cluster-service/index.html index 5495f09..e0e1a6c 100644 --- a/posts/2017-10-21-apache-camel-features-spotlight-cluster-service/index.html +++ b/posts/2017-10-21-apache-camel-features-spotlight-cluster-service/index.html @@ -7,7 +7,8 @@ Ideas are my own. ">
Warning
ClusterService is an experimental feature which will be improved in the next Camel releases.
+ \ No newline at end of file diff --git a/posts/2018-07-29-polyglot-camel-routes/index.html b/posts/2018-07-29-polyglot-camel-routes/index.html index eb6a306..3993bbf 100644 --- a/posts/2018-07-29-polyglot-camel-routes/index.html +++ b/posts/2018-07-29-polyglot-camel-routes/index.html @@ -7,7 +7,8 @@ Ideas are my own. "> \ No newline at end of file +};
Note

To user GraalJS it is required to run the project using GraalVM

+ \ No newline at end of file diff --git a/posts/2018-08-06-adventures-in-graalvm-invoke-java-code-from-js-in-native-image/index.html b/posts/2018-08-06-adventures-in-graalvm-invoke-java-code-from-js-in-native-image/index.html index f2713e6..e395aa2 100644 --- a/posts/2018-08-06-adventures-in-graalvm-invoke-java-code-from-js-in-native-image/index.html +++ b/posts/2018-08-06-adventures-in-graalvm-invoke-java-code-from-js-in-native-image/index.html @@ -7,7 +7,8 @@ Ideas are my own. ">

  1. Use a map to describe our bean

  2. Wrap the function we want to invoke using a ProxyExecutable which mimics a guest language objects that are executable

  3. Wrap our map using ProxyObject builtin fromMap

  4. Bind our proxy to a variable named bean the scripting engine can the access

  5. Finally Invoke our ProxyExecutable from JS

Caution

I’m unable to have a stable base for going further because of the following issues:

+ \ No newline at end of file diff --git a/posts/2018-09-04-adventures-in-graalvm-polyglot-camel-routes-with-native-image/index.html b/posts/2018-09-04-adventures-in-graalvm-polyglot-camel-routes-with-native-image/index.html index ee00219..4329b01 100644 --- a/posts/2018-09-04-adventures-in-graalvm-polyglot-camel-routes-with-native-image/index.html +++ b/posts/2018-09-04-adventures-in-graalvm-polyglot-camel-routes-with-native-image/index.html @@ -7,7 +7,8 @@ Ideas are my own. ">

Beside seing the route running, please note how fast the camel context has been started: 0.001 seconds

Full example can be found here

Caution

This is a very initial prototype so only a very limited subset of features has been opionantely implemented.

+ \ No newline at end of file diff --git a/posts/2019-03-28-adventures-in-graalvm-polyglot-camel-k-native-routes-with-quarkus/index.html b/posts/2019-03-28-adventures-in-graalvm-polyglot-camel-k-native-routes-with-quarkus/index.html index 0cb5370..5012737 100644 --- a/posts/2019-03-28-adventures-in-graalvm-polyglot-camel-k-native-routes-with-quarkus/index.html +++ b/posts/2019-03-28-adventures-in-graalvm-polyglot-camel-k-native-routes-with-quarkus/index.html @@ -7,7 +7,8 @@ Ideas are my own. "> \ No newline at end of file +]

  1. the camel context starts in 1ms

  2. the whole process takes around 20ms to start

Finaly we can run it on kubernetes with Camel K

camel k M2 native js

Final Notes

The Camel extension provided by Quarkus are also able to optimize routes at build time but in Camel K we do not use such feature as we want to re-use pre built Integration Contexts (including native ones) as much as possible

As stated at the beginning this blog is based on code not yet merged in the related upstream projects but the result are already quite promising so stay tuned for more updates to come.

+ \ No newline at end of file diff --git a/posts/2023-06-13-apache-camel-pulsar-function-pt_1/index.html b/posts/2023-06-13-apache-camel-pulsar-function-pt_1/index.html index 30eb1f2..2437fb0 100644 --- a/posts/2023-06-13-apache-camel-pulsar-function-pt_1/index.html +++ b/posts/2023-06-13-apache-camel-pulsar-function-pt_1/index.html @@ -7,7 +7,8 @@ Ideas are my own. "> + \ No newline at end of file diff --git a/posts/2024-01-14_apache_camel_meets_wasm_part_1/index.html b/posts/2024-01-14_apache_camel_meets_wasm_part_1/index.html index 811f545..4dde04b 100644 --- a/posts/2024-01-14_apache_camel_meets_wasm_part_1/index.html +++ b/posts/2024-01-14_apache_camel_meets_wasm_part_1/index.html @@ -1,5 +1,5 @@ -Apache Camel meets WASM - Part 1 | Luca Burgazzoli -Apache Camel meets Wasm - Part 1 | Luca Burgazzoli +

Apache Camel meets WASM - Part 1

I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them.

Background

To get started, let’s have a basic understanding of the components/technologies we are going to mention in this post:

  • Apache Camel is an open-source integration framework that provides a set of tools and patterns for facilitating the integration of various applications, systems, and technologies. It simplifies the process of connecting different software components and systems, allowing them to communicate and exchange data in a flexible and efficient manner.
  • WebAssembly (Wasm) is a low-level bytecode format designed as a portable target for the compilation of high-level languages like C, C++, and Rust, enabling deployment on the web for client and server applications.
  • Chicory is a JVM native WebAssembly runtime. It allows you to run WebAssembly programs with zero native dependencies or JNI. Chicory can run Wasm anywhere that the JVM can go.

Goals

Our primary objective is to support Wasm as a means to provide custom processing and transformation logic within Apache Camel.

Implementation

As a first experiment, I’ve started by implementing a dedicated Apache Camel component for Wasm. If you are a little familiar with Apache Camel, then you know that a Component is pretty much a factory to create Producers and Consumers, which are entities interfacing with the target system (a remote API, a Java library, ect).

camel-component

In our case, we just want to invoke a function provided as a Wasm bytecode and since Apache Camel is written in Java, then here is where Chicory enters the game. + ">

Apache Camel meets Wasm - Part 1

I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them.

Background

To get started, let’s have a basic understanding of the components/technologies we are going to mention in this post:

  • Apache Camel is an open-source integration framework that provides a set of tools and patterns for facilitating the integration of various applications, systems, and technologies. It simplifies the process of connecting different software components and systems, allowing them to communicate and exchange data in a flexible and efficient manner.
  • WebAssembly (Wasm) is a low-level bytecode format designed as a portable target for the compilation of high-level languages like C, C++, and Rust, enabling deployment on the web for client and server applications.
  • Chicory is a JVM native WebAssembly runtime. It allows you to run WebAssembly programs with zero native dependencies or JNI. Chicory can run Wasm anywhere that the JVM can go.

Goals

Our primary objective is to support Wasm as a means to provide custom processing and transformation logic within Apache Camel.

Implementation

As a first experiment, I’ve started by implementing a dedicated Apache Camel component for Wasm. If you are a little familiar with Apache Camel, then you know that a Component is pretty much a factory to create Producers and Consumers, which are entities interfacing with the target system (a remote API, a Java library, ect).

camel-component

In our case, we just want to invoke a function provided as a Wasm bytecode and since Apache Camel is written in Java, then here is where Chicory enters the game. Thanks to the excellent Chicory’s Low Level API, writing an Producer becomes straighforward so, ignoring all the boilerplate required to create a Component, invoking a Wasm function boils down to a simple class like this one:

import java.util.Objects;
 
 import com.dylibso.chicory.runtime.ExportFunction;
@@ -142,5 +143,9 @@
 
 }

Conclusion

While this is merely a proof-of-concept, the integration of Apache Camel with Wasm holds great potential. -Stay tuned for future posts, where we’ll delve deeper into the possibilities

To learn more about this implementation and explore its code, visit my GitHub repository

\ No newline at end of file +Stay tuned for future posts, where we’ll delve deeper into the possibilities

To learn more about this implementation and explore its code, visit my GitHub repository

+ \ No newline at end of file diff --git a/posts/index.html b/posts/index.html index 6a11515..e10f442 100644 --- a/posts/index.html +++ b/posts/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

Posts

2024

2023

2019

2018

2017

2016

\ No newline at end of file + ">

Posts

2024

2023

2019

2018

2017

2016

+ \ No newline at end of file diff --git a/posts/index.xml b/posts/index.xml index 077e5b4..907d7e6 100644 --- a/posts/index.xml +++ b/posts/index.xml @@ -1,4 +1,4 @@ -Posts on Luca Burgazzolihttps://lburgazzoli.github.io/posts/Recent content in Posts on Luca BurgazzoliHugo -- gohugo.ioen-usSun, 14 Jan 2024 00:00:00 +0000Apache Camel meets WASM - Part 1https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/Sun, 14 Jan 2024 00:00:00 +0000https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them. +Posts on Luca Burgazzolihttps://lburgazzoli.github.io/posts/Recent content in Posts on Luca BurgazzoliHugo -- gohugo.ioen-usSun, 14 Jan 2024 00:00:00 +0000Apache Camel meets Wasm - Part 1https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/Sun, 14 Jan 2024 00:00:00 +0000https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them. Background To get started, let’s have a basic understanding of the components/technologies we are going to mention in this post: Apache Camel is an open-source integration framework that provides a set of tools and patterns for facilitating the integration of various applications, systems, and technologies.Apache Camel Pulsar Function, Part 1https://lburgazzoli.github.io/posts/2023-06-13-apache-camel-pulsar-function-pt_1/Thu, 15 Jun 2023 00:00:00 +0000https://lburgazzoli.github.io/posts/2023-06-13-apache-camel-pulsar-function-pt_1/I recently came across an interesting article from DataStax about simplified, low-code friendly data piepelines with Pulsar Function and since I always wanted to learn a little bit more about Apache Pulsar and I’ve been working on something similar, I’ve started exploring how a Pulsar Function based on Apache Camel would look like. Background To get started, let’s have a basic understanding of Apache Pulsar and Apache Camel: diff --git a/tags/camel/index.html b/tags/camel/index.html index 79998d5..4215223 100644 --- a/tags/camel/index.html +++ b/tags/camel/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

camel

2024

2023

2019

2018

2017

2016

\ No newline at end of file + ">

camel

2024

2023

2019

2018

2017

2016

+ \ No newline at end of file diff --git a/tags/camel/index.xml b/tags/camel/index.xml index 4fed5f7..3f53bba 100644 --- a/tags/camel/index.xml +++ b/tags/camel/index.xml @@ -1,4 +1,4 @@ -camel on Luca Burgazzolihttps://lburgazzoli.github.io/tags/camel/Recent content in camel on Luca BurgazzoliHugo -- gohugo.ioen-usSun, 14 Jan 2024 00:00:00 +0000Apache Camel meets WASM - Part 1https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/Sun, 14 Jan 2024 00:00:00 +0000https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them. +camel on Luca Burgazzolihttps://lburgazzoli.github.io/tags/camel/Recent content in camel on Luca BurgazzoliHugo -- gohugo.ioen-usSun, 14 Jan 2024 00:00:00 +0000Apache Camel meets Wasm - Part 1https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/Sun, 14 Jan 2024 00:00:00 +0000https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them. Background To get started, let’s have a basic understanding of the components/technologies we are going to mention in this post: Apache Camel is an open-source integration framework that provides a set of tools and patterns for facilitating the integration of various applications, systems, and technologies.Apache Camel Pulsar Function, Part 1https://lburgazzoli.github.io/posts/2023-06-13-apache-camel-pulsar-function-pt_1/Thu, 15 Jun 2023 00:00:00 +0000https://lburgazzoli.github.io/posts/2023-06-13-apache-camel-pulsar-function-pt_1/I recently came across an interesting article from DataStax about simplified, low-code friendly data piepelines with Pulsar Function and since I always wanted to learn a little bit more about Apache Pulsar and I’ve been working on something similar, I’ve started exploring how a Pulsar Function based on Apache Camel would look like. Background To get started, let’s have a basic understanding of Apache Pulsar and Apache Camel: diff --git a/tags/cloud/index.html b/tags/cloud/index.html index 063562f..ee85eca 100644 --- a/tags/cloud/index.html +++ b/tags/cloud/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

cloud

2017

2016

\ No newline at end of file + ">

cloud

2017

2016

+ \ No newline at end of file diff --git a/tags/clustering/index.html b/tags/clustering/index.html index 800f995..4487841 100644 --- a/tags/clustering/index.html +++ b/tags/clustering/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

clustering

2017

\ No newline at end of file + ">

clustering

2017

+ \ No newline at end of file diff --git a/tags/fabric8/index.html b/tags/fabric8/index.html index 20fec0f..5c361dc 100644 --- a/tags/fabric8/index.html +++ b/tags/fabric8/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

fabric8

2016

\ No newline at end of file + ">

fabric8

2016

+ \ No newline at end of file diff --git a/tags/functions/index.html b/tags/functions/index.html index 766a6b9..2a4149f 100644 --- a/tags/functions/index.html +++ b/tags/functions/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

functions

2023

\ No newline at end of file + ">

functions

2023

+ \ No newline at end of file diff --git a/tags/graalvm/index.html b/tags/graalvm/index.html index 9ba787a..0c4b8bb 100644 --- a/tags/graalvm/index.html +++ b/tags/graalvm/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

graalvm

2019

2018

\ No newline at end of file + ">

graalvm

2019

2018

+ \ No newline at end of file diff --git a/tags/index.html b/tags/index.html index 43fc461..a3c0923 100644 --- a/tags/index.html +++ b/tags/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

Tags

2024

2023

2019

2017

2016

\ No newline at end of file + ">

Tags

2024

2023

2019

2017

2016

+ \ No newline at end of file diff --git a/tags/java8/index.html b/tags/java8/index.html index 8b9f0ff..830466f 100644 --- a/tags/java8/index.html +++ b/tags/java8/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

java8

2016

\ No newline at end of file + ">

java8

2016

+ \ No newline at end of file diff --git a/tags/karaf/index.html b/tags/karaf/index.html index 09b0b99..f8252ad 100644 --- a/tags/karaf/index.html +++ b/tags/karaf/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

karaf

2016

\ No newline at end of file + ">

karaf

2016

+ \ No newline at end of file diff --git a/tags/kubernetes/index.html b/tags/kubernetes/index.html index 720eb7c..c05de18 100644 --- a/tags/kubernetes/index.html +++ b/tags/kubernetes/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

kubernetes

2016

\ No newline at end of file + ">

kubernetes

2016

+ \ No newline at end of file diff --git a/tags/lowcode/index.html b/tags/lowcode/index.html index c17abd1..b55ef22 100644 --- a/tags/lowcode/index.html +++ b/tags/lowcode/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

lowcode

2023

\ No newline at end of file + ">

lowcode

2023

+ \ No newline at end of file diff --git a/tags/microservices/index.html b/tags/microservices/index.html index aabc2b9..a3b274e 100644 --- a/tags/microservices/index.html +++ b/tags/microservices/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

microservices

2017

2016

\ No newline at end of file + ">

microservices

2017

2016

+ \ No newline at end of file diff --git a/tags/openshift/index.html b/tags/openshift/index.html index a357924..f8b7498 100644 --- a/tags/openshift/index.html +++ b/tags/openshift/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

openshift

2016

\ No newline at end of file + ">

openshift

2016

+ \ No newline at end of file diff --git a/tags/pulsar/index.html b/tags/pulsar/index.html index 84e4f34..b74cd51 100644 --- a/tags/pulsar/index.html +++ b/tags/pulsar/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

pulsar

2023

\ No newline at end of file + ">

pulsar

2023

+ \ No newline at end of file diff --git a/tags/scripting/index.html b/tags/scripting/index.html index 2a2a49a..d3c49eb 100644 --- a/tags/scripting/index.html +++ b/tags/scripting/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

scripting

2019

2018

\ No newline at end of file + ">

scripting

2019

2018

+ \ No newline at end of file diff --git a/tags/spring-boot/index.html b/tags/spring-boot/index.html index 914e984..ff276b9 100644 --- a/tags/spring-boot/index.html +++ b/tags/spring-boot/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

spring-boot

2016

\ No newline at end of file + ">

spring-boot

2016

+ \ No newline at end of file diff --git a/tags/spring-cloud/index.html b/tags/spring-cloud/index.html index 6bba010..94b6a67 100644 --- a/tags/spring-cloud/index.html +++ b/tags/spring-cloud/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

spring-cloud

2016

\ No newline at end of file + ">

spring-cloud

2016

+ \ No newline at end of file diff --git a/tags/wasm/index.html b/tags/wasm/index.html index b26e349..f38b9c9 100644 --- a/tags/wasm/index.html +++ b/tags/wasm/index.html @@ -7,6 +7,11 @@ Ideas are my own. ">

wasm

2024

\ No newline at end of file + ">

wasm

2024

+ \ No newline at end of file diff --git a/tags/wasm/index.xml b/tags/wasm/index.xml index c69be18..6dbdf65 100644 --- a/tags/wasm/index.xml +++ b/tags/wasm/index.xml @@ -1,3 +1,3 @@ -wasm on Luca Burgazzolihttps://lburgazzoli.github.io/tags/wasm/Recent content in wasm on Luca BurgazzoliHugo -- gohugo.ioen-usSun, 14 Jan 2024 00:00:00 +0000Apache Camel meets WASM - Part 1https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/Sun, 14 Jan 2024 00:00:00 +0000https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them. +wasm on Luca Burgazzolihttps://lburgazzoli.github.io/tags/wasm/Recent content in wasm on Luca BurgazzoliHugo -- gohugo.ioen-usSun, 14 Jan 2024 00:00:00 +0000Apache Camel meets Wasm - Part 1https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/Sun, 14 Jan 2024 00:00:00 +0000https://lburgazzoli.github.io/posts/2024-01-14_apache_camel_meets_wasm_part_1/I recently stumbled upon a fascinating JavaAdvent article discussing a native WebAssembly runtime for the JVM called Chicory. Intrigued by the potential synergy between WebAssembly and Apache Camel, I decided to experiment with integrating them. Background To get started, let’s have a basic understanding of the components/technologies we are going to mention in this post: Apache Camel is an open-source integration framework that provides a set of tools and patterns for facilitating the integration of various applications, systems, and technologies. \ No newline at end of file