The Camel guy going on APAC tour this August

Tomorrow I will be leaving for a tour in the APAC region where I am going to spread the words about agile integration using Apache Camel and Kubernetes and OpenShift.

I have plotted my destinations in the map below

The first stop is Tokyo where I will arrive on this Saturday August 5th (11 hour flight). I will then be jet-lagged and a bit tired so I will take it easy on Saturday.  On Sunday I plan to polish my presentations, and then visit some spots in Tokyo.

Monday and Tuesday are full day workshops. Red Hat has posted information about these workshops on the registration page for the Sydney and Melbourne events in case you are interested. I am not aware of any registration page for Tokyo which was quickly fully booked so we had to do a 2nd day as well.

On Wednesday I do have some time in the morning and afternoon to see a bit more of Tokyo before I will travel to Sydney (10h flight) where I arrive August 10th Thursday morning. In the evening I will attend and speak at the Sydney meetup. So if you are in this area you are very welcome to come by, as I love chatting with fellow developers and possible Camel users.  Then we have the full day workshop on Friday 11th.

On Saturday the 12th is my first leisure day where I have booked the bridgeclimb tour at 10am. If I am up early in the morning I will go see the opera house (as it was designed by a Danish architect) and the viewpoint of the harbour from the botanic garden. In the afternoon I will go to The Rocks for a cup of coffee and/or beer(s). I am in talks with a few Camel users from a Sydney office whom want to meet there for some drinks. You are welcome to join us there, you can reach out to me on my email or twitter etc.

On Sunday I travel to Melbourne. On Monday 14th I plan to run the F1 circuit track in Albert Park. If all goes well then I will run several rounds so I can do a half marathon distance. The following day we have a full day workshop in Melbourne. At this time of writing there is a potential meetup in Melbourne happening as well on the evening of Tuesday 15th. They are currently finding a venue.

On Wednesday I travel to Wellington where we have two full day workshops on Thursday and Friday.

Saturday 19th I have a full day in Wellington where I plan to walk the city and see various stuff. And see if I can recall some of the places I visited 15 years ago when I backpacked New Zealand and Australia.

I then fly to Auckland on Sunday 20th August and have a mini vacation there until Wednesday where I travel to USA (12 hour flight). If you are from around Auckland and want to have a cup of coffee or a drink somewhere then you are welcome to reach out to me via my email or twitter etc.

In USA I will visit an old friend whom I have not see in about 15 years, when he relocated to Seattle when he got a job at Microsoft. Among others he is taking me to my first live american football game where we are going to see Seattle Seahawks.

I will travel back to Denmark on Monday 28th and arrive back home in the afternoon on the 29th.
And then its back to Camel land and work from the 30th August.

My travel plan is as follows (where there is an empty space means traveling):

2017-08-05: Tokyo
2017-08-06: Tokyo
2017-08-07: Tokyo
2017-08-08: Tokyo
2017-08-10: Sydney
2017-08-11: Sydney
2017-08-12: Sydney
2017-08-14: Melbourne
2017-08-15: Melbourne
2017-08-17: Wellington
2017-08-18: Wellington
2017-08-19: Wellington
2017-08-21: Auckland
2017-08-22: Auckland
2017-08-24: Seattle
2017-08-25: Seattle
2017-08-26: Seattle
2017-08-27: Seattle
2017-08-29: Denmark


Webinar by me - Build distributed microservices using Apache Camel deployed on containers

On thursday 20th July I am doing a live webinar:

For Java developers, it may be daunting to get started developing container applications that run locally on Kubernetes/OpenShift. 

In this session, we’ll build a set of Apache Camel- and Java-based microservices that use Spring Boot and WildFly Swarm. We’ll show how fabric8 Maven tools can be used to build, deploy, and run your Java projects on local or remote OpenShift clusters, as well as to easily perform live debugging. 

Additionally, we’ll discuss best practices for building distributed and fault-tolerant microservices using technologies such as Kubernetes Services, Netflix Hystrix, and Apache Camel Enterprise Integration Patterns (EIPs) for fault tolerance.

The webinar is on a timezone that is friendly to developers based in the asia/pacific region which is at 1:00 pm SGT (Singapore Time). That means I have to get up early in the morning ;)

The webinar is a mix between slides and live demos (5 demo sessions) so there is a lot of action going on. I have captured all the important information in the slides, so after attending the webinar you should be able to try this on your own, by just browsing the slides, and downloading the sample code.

You can register (for free) to the webinar with this link. I am not aware of any upper cap, but you may have to hurry to be safe to get a spot, because I was told there is already move than 1300 registations a couple of days ago.


Camel in Action 2nd edition is in pre-production

I just wanted to share a little status update on where we are with the Camel in Action 2nd edition book.

We recently completed the last round of reviews from a selected group of readers whom have provided anonymous feedback on the material.

Based on their feedback we were able to do some changes to the material before we handed it over to pre-production.

One point we knew and also have gather feedback about is the length of the book. For example the last MEAP release has staggering 996 pages in the PDF file.

We have identified up till about 100 pages that was the weakest content in the book, which we would then cut out from the final book. Out of those 100 pages we will made available the last two chapters as online bonus chapters, freely available for download. The IoT and Reactive chapters felt a bit out of place accordingly to reviewers. Don't despair these bonus chapters will go under the same scrutiny as all the other chapters to ensure the same high quality level you would expect from a Manning book.

At this point all the chapters are in pre-production phase, where they are undergoing technical review, proofing, etc.

As part of the pre-production phase, we will do the cut and any final post cleanup changes before the material is final and the book is handed over to type setting.

The dead-line for the pre-production is end of July, which means that the book will go into type setting afterwards and then getting much closer to be done. While the chapters are in type setting we will work on what is called the front matter, which is essentially all the other stuff. And when that work is complete, then we can sit back and just wait until the book is printed and we have it in out hands.


Apache Camel 2.19 Released - Whats new

Apache Camel 2.19 was released on May 5th 2017 and its about time I do a little blog about what this release includes of noteworthy new features and improvements.

Here is a list of the noteworthy new features and improvements.

1. Spring Boot Improvements

The Camel 2.19 release has been improved for Spring Boot in numerous ways. For example all the Camel components now include more details in their spring boot metadata files for auto configuration. This means tooling can now show default values, documentation etc for all the options on each component, language, and data format you may use, and configure in application.properties or .yml files.

The release is also up to date with latest Spring Boot 1.5.3 release.

Some component has improved auto configuration which makes it even easier to use, such as camel-servlet where you can easily setup the context-path from the application.properties file.

We have also made available to configure many more options on CamelContext as well so you can tweak JMX, stream caching, and many other options.

2. Camel Catalog Improvements

The Camel Catalog now includes fine grained details of every artifact shipped in the release, also for the other kinds such as camel-hystrix, camel-cdi etc.

The catalog now also include all the documentation in ascii doc and html format.

The catalog has specialized providers for Spring Boot and Karaf runtimes, which allows tooling to know which of the Camel artifacts you can use on those runtimes.

The Camel project uses the catalog itself, so we now use this to automatic generate and keep a full list of all the artifacts on the website, and when each artifact was added. You can therefore see whether its a new artifact in this release, or was introduced in Camel 2.17 etc.

There is a specialized runtime version of the CamelCatalog provided in camel-core RuntimeCamelCatalog, which allows you to tap into the catalog when running Camel. The offline catalog is camel-catalog which is totally standalone.

3. Camel Maven Plugin can now validate

There is a new validate goal on the camel-maven-plugin which allows you to check your source code and validate all your Camel endpoints and simple expressions whether they have any invalid configuration or options. I have previously blogged about this.

4. Auto reload XML files

If you develop Camel routes in XML files, then you can now turn on auto reload, so Camel will watch the XML files for changes and then automatic update the routes on the fly. I have previously blogged and recorded a video of this.

5. Service Call EIP improvements

Luca has been buys improving the Service Call EIP so it works better and easier with Camel on the cloud, such as kubernetes or spring-boot-cloud. 

Luca blogged recently about this.

6. Calling REST services is easier

If you want to use Camel to call RESTful services then its now easier as we add a producer side to the Rest DSL. This means you can call REST service using the rest component that can then plugin and use any of the HTTP based component in Camel such as restlet, http4, undertow etc.

For more information see the rest-producer example.

We also added a new camel-swagger-rest component that makes it even easier to call Swagger REST APIs, where you can refer to their operation id, and then let Camel automatic map to its API.

For more information see the rest-swagger example and the rest-swagger documentation.

7. CDI with JEE transactions

The camel-cdi component now supports JEE transactions so you can leverage that out of the box without having to rely on spring transactions anymore.

8. Example documentation improved

We now generate a table with all the examples and sorted by category. This allows users to find the beginner examples, rest, cloud etc. And also ensure that we keep a better documentation for our examples in the future as the generator tool will WARN if we have examples without documentation.

Also all examples have a readme file with information about the example and how to run.

9. Spring Cloud components

There is new Camel components that integrate with Spring Cloud and Spring Cloud Netflix. This makes it easy to use for example the ServiceCall EIP or Hystrix EIP with Spring Cloud Netflix or just Camel with Spring Cloud in general. You can find more information in the example.

10. Kafka improvements

The camel-kafka component has been improved to work more intuitively. This unfortunately means the uri syntax has changed in a backwards incompatible way. So if you are upgrading then make sure to change your uris. However the new syntax resemble how other messaging components does it by using kafka:topicName?options. 

Also the component can now automatic convert to the kafka serializer and deserializer out of the box, so you dont have to hazzle with that. We provide converts to the typically used such as byte[] and string types.

The component also has been upgraded to latest Kafka release and its now possible to store the offset state offline so you can resume from this offset in case you stop and later start your application.

Its also much easier to configure and use custom key and partition key which can be supplied as header values.

And there is a new Kafka idempotent repository.

11. Route Contracts 

We have added initial support for being able to specify an incoming and outgoing type to a Camel route (called transformer and validator inside Camel). This then allows both Camel at runtime, and Camel developers to know what payload the routes is expected as input and what it returns. For example you can specify that a route takes in XML and returns JSon. And with XML you can even specify the namespace. Likewise you can specify Java types for POJO classes. Based on these contracts Camel is able at runtime to automatic be able to type-covert the message payload (if possible) between these types if needed.

We will continue with more improvements in this area. For example we hope we can add such capabilities to Camel components so they will be able to provide such information so your Camel routes is more type-safe with the message payloads during during routing.

And tooling will also be able to tap into this formation and then for example "flag" users with hints about routes not being compatible etc.

You can find more details in this example (we have for CDI and XML as well) and in the documentation.

12. Reactive Camel

There is a new camel-reactive-streams component that makes Camel work as first-class with the reactive-streams API so you can easily use Camel components in your reactive flows, or call flows from your Camel routes.

For the next release there is a camel-rx2 component in the works which has improved support for Camel with the popular RxJava 2 framework.

For users that want to use reactive with vert.x then there is a camel-vertx and vertx-camel-bridge components in both projects. We plan to merge them together and bring the best features from each of them together in the future, when we get some time. However Claus is in talks with the vert.x team about this. 

You can find more information in some of this example. And the Camel in Action 2nd ed book contains an entire chapter 21 covering all of this.

13. Java 8 DSL improvements

And just on top of my head the Java 8 DSL has been slightly improved to allow using more of the Java 8 lambda and functional style in your Camel routes and EIPs. We will continue to improve this from time to time when we find EIPs that can be made more awesome for savvy Java 8 users. We are also looking for feedback in this area so if you are kneed deep in the Java 8 style then help us identify where we can improve the DSL.

14. Camel Connectors

We have introduced a new concept called Camel Connector. However its still early stages and we will over the next couple of releases further improve and refine what a Camel connector is.

The short story is that a Camel Connector is a specialized and pre-configured Camel Component that can do one thing and one thing only. For example if you need to known when someone mentions you on twitter, then you can use the camel-twitter component. But it can do 10 things and it can take time to understand how to use the component and make it work. So instead you can build a connector that can just do that, a camel-twitter-mention connector.  It's pre-build and configured to just do that. So all you need to do is to configure your twitter credentials and off you go. At runtime the connector is a Camel component, so from Camel point of view, they are all components and therefore it runs as first-class in Camel.

We have provided some connector examples in the source code.

15. Many more components

As usual there is a bunch of new components in every Camel release and this time we have about 20 new components. You can find the list of new components in the release notes, or on the Camel components website where you can search by the 2.19 release number.

For example there is a camel-opentracing component that allows to use Camel with distributed tracing. Gary Brown has blogged about this.

There is also a few new Camel components for IoT such as camel-milo that Jens Reimann blogged about.

There is a bunch of other smaller improvements which you can find in the release notes. For example the jsonpath language now allows to use embedded simple language, and you can define predicates in a much simpler syntax without too many of the confusing jsonpath tokens, in case you just want to say order.customer.id > 1000 etc.


Developing cloud-ready Camel microservice talk from Red Hat Summit 2017

I am sitting at Boston Logan Airport and having a Samuel Adams lager and checking up my twitter timeline, emails and whatelse is happening.

Two days ago I had my talk about developing cloud ready Camel microservices at Red Hat Summit 2017. The talk was video recorded and it is already online on you tube.

The source code and slides is posted on my github account at: https://github.com/davsclaus/minishift-hello

I had a great time at Red Hat Summit and enjoyed meeting up with fellow Red Hat co-workers and others whom I know from twitter or the open source communities.


Mine and other Camel talks at Red Hat Summit 2017

Next week I am giving a talk at Red Hat Summit 2017 in Boston.

S104668 - Developing cloud-ready Camel microservices

Its a talk how to get started as a Java developer to build Java based microserves that runs on Kubernetes or OpenShift. Its a talk that is a mix between slides and live demo where its all coded and running locally on my old laptop.  I am using three of my favorite Java stack with Apache Camel, Spring Boot, and WildFly Swarm in the demos.

The talk is on Tuesday May 2nd before lunch, eg 11:30 to 12:15pm so you can come and bild up an appetite.

On Wednesday from 3-5pm I am on boot duty at the Red Hat Community Central, so that's a chance for you to come find me and have a chat. I am actually not aware where that is located, but I would assume its in the exhibition hall.

I will be in Boston all week and attend Summit from Tuesday till Thursday. On Friday evening I am flying back home.

I have started running for the last year or so, so I am also signed up for the 5km Summit run which happens at 6 am on Wednesday. In my time zone that would be noon so I am up and awake already.

Other Camel Talks

There is a number of other talks that I plan to attend.

For example Rajith's talk with TD Bank where they talk how they are using Camel. I love to hear about what the real world does with Camel and Red Hat summit is a conference where also the customer stories are present.

S103873 - Migrating TD Bank's monolithic Java EE application to a microservices architecture

There is also the stuff I have been worked on lately a new product iPaaS that uses Camel under the hood. I am really looking forward to Keith and Hiram presenting this.

S101856 - Red Hat iPaaS—integration made easy

Christian Posta is always an inspiration. I always learn something when he give talks about microservices. He is out there in the field and see first hand what our customers want to do, and what they are doing/can do.

S101993 - The hardest part of microservices is your data

I have formerly worked in the health care industry and have a chance to hear Quinn Stevenson's talk. Quinn has been fantastic in the Camel community where he has contributed code patches, components and help Camel work better with OSGi and HL7.

S103149 - Deploying Red Hat JBoss Fuse in healthcare—notes from the field

I don't want to miss the chance to hear about how to migrate a monolith 10 year old system to a modern microservice based with Camel, Vert.X, and other cool technologies.

S99785 - How to handle the complexity of migrating to microservices from 10 years of monolithic code

There are more talks about Camel that I will try to attend. There are 12 sessions listed in the Red Hat Summit agenda.

If you are attending Red Hat Summit. Then I hope we get a chance to meet and say hi. I love the hallway conversations at conferences and also to hear the good, bad, and ugly. Apache Camel is not perfect, likely far from it. But its adaptive and very flexible, and we have a very active, vibrant and open community.

And btw Camel 2.19 is on the way. We are building the release candidate this week. So hopefully its released by Summit so I can tell Jim Whitehurst to announce that at the keynote ;)


Next phase with the Camel in Action 2nd edition book

This time its a longer ride for Jonathan and myself. Its about 2 years ago we started with the first words and edits for writing this book all over again.

Here 2 years later we have just handed in our last complete draft of all the chapters and appendixes. All 21 chapters are in the bank, and now we enter a new phase. The table of content at the Manning website has not yet been updated, so there is 2 additional chapters in the final book than listed currently. More for the money for you ;)

The book is going into pre-production. Here is roughly what will happen:

The newest 1/3 of the chapters will first have to go through a review procedure where a selected group of anonymous readers are providing feedback. And based on their feedback and what else may come to our attention we can freely do changes to these chapters. Then they join the rest of the chapters.

The other 2/3 of the chapters are already moving ahead and are under Mannings strict scrutiny of tech review and proofing. For example chapter 13 has already been through this process. The chapter has a thousand or so, small changes to fix up the grammar, flow of content and just make it enjoyable to read, instead of my 2nd-language english.

At the same time Apache Camel moves ahead and the upcoming 2.19.0 release is planned for end of April / start of May. This means that we will ensure all the content in the book is up to date with reference to this release. A big part of that is also to ensure all the accompanying source code is fully up to date as well.

Likewise Jonathan and I have a TODO list of small items we have noted over the time to go back into the previous chapters to do updates.

With all this combined we will ensure that all the content in the book is fully up to update and cover as much of Apache Camel as possible. For things that are not possible to cover we will add callouts or sidebars with details and references where you can find more material. And on the good days we will add an example with the source code etc.

So there is surely more work for us before we can see the finish line. As they say its not over until the fat lady signs.