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.