npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

camelnodejs

v1.0.8

Published

Run Camel routes from NodeJS.

Downloads

3

Readme

Apache Camel for NodeJS

Run Camel routes from NodeJS.

If you want to run Apache Camel routes from Kubernetes then consider Apache Camel K.

If your happy to use Java or a JVM then I suggest you use that rather than this, this is a way to avoid using JVM and still run Apache Camel from NodeJS.

Usage

npm install camelnodejs

Given a route.yaml

- route:
    from: "timer:yaml?period=3s"
    steps:
      - set-body:
          simple: "Timer fired ${header.CamelTimerCounter} times"
      - to:
          uri: "log:yaml"

Then the corrisponding index.js javascript

const camelnodejs = require('camelnodejs');

(async () => {
    await camelnodejs.startApacheCamel();
})()

Run with node, node index.js then it executes the Apache Camel route.

Notes

This is in early development, works on Windows only. (at this moment).

Description

Apache Camel allows for data integration between services through the use of pipelines. Apache Camel is on the JVM, the problem is that when using NodeJS it is unattractive to run a Java program or JVM from NodeJS. Especially when on cloud such as AWS Lambda, the memory limits are low and installing or running a JVM is very much not a good idea.

Solution

To avoid use of the JVM, Java code using Apache Camel as a library is compiled with Quarkus to a binary executable, this executable can then run the Camel route. NodeJS executes this executable. In a sample run the binary executable camel-quarkus-runner.exe file size was 55.6 MB and when running used 32.0 MB of memory which is reasonable.

Restrictions

  • Not all Apache Camel components will be added, the addition of more components increases the file size of the executable so only common components are added.

Future directions and tasks

  • Produce multiple binaries, Windows, Linux and OSX
  • It would be better to move this to a library (DLL on Windows) rather than an executable, but how to compile Quarkus to a DLL? can it even be done?
  • Handle application crashes and errors
  • Add logging, don't output to stdout as it currently does
  • Support Javascript routing, currently only supports YAML file routing
  • Add example Apache Camel routes and test cases
  • Tighter integration with NodeJS
  • Support multiple YAML files and/or any number of YAML files within a directory
  • Support YAML file name as a parameter rather than default of route.yaml