Webinar - Develop Cloud Native Microservices using Apache Camel

On next thursday 31st January 2019 I am presenting a live webinar about developing cloud native microservices with Apache Camel.

The session is scheduled for a full hour including QA. The talk with be a mix of slides and live demos. It will be my first talk with revealing details about Apache Camel 3 and a peak and demo of Camel K (next-gen serverless Camel on Kubernetes).

The abstract of the talk is as follows

Apache Camel has fundamentally changed the way enterprise Java developers think about system-to-system integration by making enterprise integration patterns (EIP) a simple declaration in a lightweight application—wrapped and delivered as a single JAR.

In this webinar, we’ll show you how to bring EIP best practices to containers running on top of Kubernetes and deployed as Spring Boot microservices, which are both cloud-native and cloud-portable.

We'll discuss:

  • How building and designing cloud-native microservices impacts the way we develop.
  • How to build distributed and fault-tolerant microservices.
  • The upcoming Camel 3.0 release, which includes serverless capabilities via Camel K.


The webinar is scheduled on thursday 31st of January at 11am ET (5pm CET) and is of course free to attend. All you need to do is to register at the provided link.

More webinars

We have talked about continuing the webinar with a series of Camel and agile integration talks. So if you are interested to hear more webinars and have requests for topics to be covered then we are open for feedback.


Apache Camel explained to Luke Skywalker

A long time ago in a galaxy far,
far away ...
there was a a young boy,
whom went to

What a story. So Mark Hamill is addressed as Mr Camel. What an honour to have him in our Camel family and to be known as the first Mr Camel. The 2nd Mr Camel is our spirit animal for the Apache Camel project.

Okay back to Luke Skywalker, so his tweet lead to people talking about Camel's and I was then brought into the conversation whether Mark's audition story was my inspiration for Apache Camel, which again lead to Mark Hamill (Luke Skywalker) asking what Apache Camel is:

I must say I have never seen the day, where Luke Skywalker would ask me what Apache Camel is 😃 - I am a great fan of Star Wars and yes I am so old that I favour the first 3 classic movies.

Explaining what Apache Camel is to Luke Skywalker

At first though you may think that Apache Camel is a new model of the 4-legged walker with or without humps 🙃 ... but it is NOT

Instead let us ask the most wise man in the universe, Yoda, for the answer:

"Software that enables you to do integrations between other softwares, it is." - Yoda

And in my humble words ...

"What the force telekinesis does for universal Jedi connection ... the Apache Camel does for universal computer integration .... mindblow powers they are" - DavsClaus

And here is another great explanation from Matthew what Apache Camel is:

Has Luke Skywalker used Apache Camel?

Yes Mark you would unknowingly have used Apache Camel. Here is why. 

Apache Camel is a software project that has been around for over a decade. And its a very succesfull project and are thus widespread in use across all industries, enterprises, government institutions, and used in all parts of our planet.

In the US, for example, the FAA uses Camel in their services for air-traffic control. So anyone whom has been traveling by plane in the US airspace (covers 15% of the planet) would have used Camel.

Camel is also ubiquitous used among banking and finance enterprises, so any US citizen whom has done bank transfers, credit card transactions etc would at one point have the banking systems exchange data via software with Camel included.

If you are a Netflix subscriber then their payment system is using Camel as well. If you have a parcel delivery by brown-trucks (UPS) then Camel is helping with the track and trace.


Thank you Mark Hamill for asking me what Apache Camel is. I have been working on Apache Camel for more than 10 years and I still not able to explain it to the common man in a few words. Even trying to explain it to my peers in the IT industry is failing, evident by my last book is a staggering 900 page monster 🙃

May the force be with you


Apache Camel 2018 Numbers

Its been 2 years since I last did a blog post about the Camel numbers.

Just to do a quick post on some of the numbers for the Apache Camel project in year 2018.

Number of releases in 2018: 12
Number of posts on Camel user forum in 2018: 1266
Number of gitter chat users at end of 2018: 428
Number of commits in 2018: 3600 (git shortlog -ns --since 2018-01-01 --until 2019-01-01 | cut -c1-7 | awk '{ SUM += $1} END { print SUM }')

Total number of JIRA tickets created at end of 2018: 13033
Number of JIRA tickets created in 2018: 924
Number of JIRA tickets resolved in 2018: 766

Stackoverflow number of questions at end of 2018: 8375
Stackoverflow number of watchers at end of 2018: 1.8k

Number of stars on github at end of 2018: 2303
Total number of commits at end of 2018: 34431
Total number of contributors on github at end of 2018: 447
Number of closed pull requests at end of 2018: 2674
Number of closed pull requests in 2018: 280 (is:pr is:closed merged:>=2018-01-01)
Number of committers doing commits in 2018: 184 (git shortlog --since 2018-01-01 --until 2019-01-01 -ns | wc -l).

The Apache Software Foundation recently posted a summary of the most active projects in 2018 and Apache Camel was ranked 4th by commits.

You can find more statistics for example at GitHub and OpenHub.

Happy New Year and 2019 is going to be a special year for Apache Camel, with Camel 3 in the works.


Camel in Action 2nd edition source code up to date with the Camel 2.23 release

I had some time to work on the source code for our book during the holidays. This year I have been more busy with other stuff so some of the work needed to keep the source code up to date with newer releases of Camel got a bit neglected. 

Today I just finished the last bits and pushed to github the changes so we are now fully caught up with the latest Apache Camel 2.23.0 release. You can either use the source code directly from the master branch, or pick one of the releases.

Merry Christmas


Work on Apache Camel 3 has finally started

We are starting the work on Apache Camel 3. We are working at multiple levels to improve Camel and introduce new features.

The first work has actually started by Guillaume Nodet in the start of October, where he jump started by cleaning up the codebase, removed deprecated code and components, improving the routing engine and other internals in the core. His work is published on the sandbox/3.x branch. We plan to use his work as the baseline for the actual Camel 3. Andrea has helped by aligning this branch with all the changes from the master branch (2.x) so its fully up to date. The intention is to switch over the sandbox/3.x branch as the new master branch, so we call can start working on that branch and being able to add new features, components etc. (as always) for Camel 3.

For 2.x users we will create a 2.x branch where we plan to do 1 or 2 more last 2.x releases, eg 2.24 and 2.25, before 3.0 is ready and released.

Here in the beginning of the Camel 3 work is to continue the work from Guillaume Nodet and finish up the cleanup of the codebase, modularize the camel-core, etc.

We invite community users and any Camel committers and developers who has interest to help with the Camel 3 work. We have talked about doing a number of milestone releases of 3.x that can help give feedback to us quicker and faster. For example any Camel users of 2.x can try to upgrade and use the 3.0 milestone releases to report back their findings.

Camel 3 is planned to be a time boxed release to avoid it dragging out “forever”, and with a bit of good luck we will have Camel 3 released after the summer 2019.

We will keep the community posted on the progress, and as always we love contributions and any feedback you may have.

The 3-humped Camel is coming in 2019 ;)


Apache Camel 2.23 released

Yesterday Apache Camel 2.23 was released which most noteworthy new feature is support for Spring Boot 2.1, where we also improved the starter components to include more metadata and more optimized for the improved Spring Boot auto configuration.

This release is mainly a big bug fix release and some other minor new features. One of these features is to allow for basic dynamic queries in the SQL component on the consumer side.

And as usual there are new components added too:

  • AWS IAM - for managing Amazon IAM
  • Corda - to interactive with corda nodes
  • FHIR - to work with the fhir standard (health care)
  • Google Big Query Standard SQL - Google bigdata warehouse analytics
  • Google Calendar Stream - Google calendar in streaming mode
  • Google Sheets - To work with google sheets
  • Google Sheets Stream - To work with google sheets in streaming mode
  • IPFS - Interplanetary File System
  • Kubernetes HPA - To execute Kubernetes HPA operations
  • Kubernetes Job - To execute Kubernetes job operations
  • NSQ - To integrate with the NSQ messaging system
The next release will be Camel 2.24 which potentially are the last 2.x release as we are about to kick-off work on Camel 3.0. More details to follow soon.


My first visit to Belarus speaking at the JFuture conference

I just got back from Minsk, Belarus where I gave a workshop and a presentation at the JFuture 2018 conference.

This was my first visit to Belarus, and its always good to see new parts of the world, and help spread the knowledge about our beloved integration software Apache Camel. I am traveling with Mr Camel so at the hotel we read the greeting card from the organisers.

On friday I hosted an Apache Camel microservices workshop with 10 Java developers whom were introduced to Apache Camel and then had fun hacking some Camel microservices code. The material is awesome and much credit to Nicola Ferraro for creating the workshop demo, which we joined presented earlier this year at JBCNConf in Barcelona.

After the workshop I went out for a run in the city, mostly in the lovely parks. The weather was beautify with sun and 15 degrees celcius. The parks are full of tree leaves as the season is autumn.

On Saturday it was conference day, and the venue is the royal theatre in Minsk.

After they keynote we had the 1st set of tracks, and I was honoured to do my performance on the main stage.

I was not the only red hatter, as Justin Lee, traveled all the way from New York to be here, and present about serverless.

For his presentation I got myself a seat in the balcony, which has a very nice view of the stage.

I walked the city on the afternoon, and took some photos. After a couple of hours I found a nice place at the backside of the palace of the republic where I enjoyed a margarita, to celebrate my first visit here.

I stayed at the Willing hotel which is located 20 minute walk from the city center. Its in an area with old factories that are now being put up for new use with startups and hipsters in the neighborhood. So there are many coffee shops and some bars. The big walls of these factories were painted by local and foreign artists.

I enjoyed my time in Minsk, and I would like to say a warm thanks to the organisers for inviting me to come. I wish you the best with the conference and can recommend it to other speakers.