Camel

In Enterprise Integration the Idempotent Receiver Pattern ensures that regardless of how many times a message is received the same result is produced. I wanted to see how Camel implements this pattern and explore some of the edge cases.

This week I needed to get data from a Power Automate flow to an internal SFTP server. We are evaluating a couple of options for this but here's how you would do it with Apache Camel...

In a previous post I wrote about taking a Test-Driven approach to Camel development. I've been asked to share the code and explain some of the steps in more detail so here we go...

Recently I've been working with a team integrating Fraud Detection software into our Core Banking System (CBS). This involves sending messages asynchronously between the systems. We are using Apache Camel for this as opposed to our standard integration platform IBM AppConnect. One of the things that make Camel attractive is its first-class support for a Test Driven Development approach. Camel allows us to incrementally evolve our integration code using tests to drive the approach. This is very cool. That said, it's not been exactly easy so whilst it's still fresh in my head I thought I would put down some points about how to make this work in your own projects.