This week marks the release of the Camel Essential Components Refcard. Author Christian Posta is a Senior Consultant and Architect at Red Hat, the card's sponsor, and he took a few minutes to answer some questions we had about the authorship of the card. His expertise in messaging-based enterprise integration is sure to make DZone's 170th Refcard a must-have cheat sheet.
Christian wanted to publicly thank Claus Ibsen, Charles Moulliard, and Torsten Melke for reviewing and contributing feedback during the creation of this Refcard. Also, if you're interested in learning more about Camel, Christian will be hosting a one-hour webinar on January 23, linked after the interview.
DZone: Christian, tell us a little bit about your background as a developer and an author.
Christian Posta: I'm a Senior Consultant at Red Hat specializing in developing enterprise software applications with an emphasis on software integration and messaging. My strengths include helping clients build software using industry best practices, ActiveMQ, Apache Camel, ServiceMix, Spring Framework, and most importantly, modeling complex domains so that they can be realized in software. I work primarily using Java and its many frameworks, but my favorite programming languages are Python and Scala.
DZone: What projects are you working on now or will be working on in the near future?
Christian Posta: I'm having a lot of fun contributing to Apache Apollo when I have time. Apollo is the next-generation of open-source messaging brokers built with an async, event-driven core. I also enjoy learning new programming languages (Scala) and becoming better at what I do. I'm also very active in the ActiveMQ mailing lists and on my blog: http://www.christianposta.com/blog
DZone: What do you think sets Camel apart from other Enterprise Integration solutions?
Christian Posta: Camel has, in my opinion, three advantages over other options:
#1 The Model: the abstractions used to model an integration (a "route") maps closely with the way most developers think about what an integration would look like. The DSLs make it easy to quickly figure out "what" is being "integrated" without being bogged down by details and distraction
#2 Components: Camel has a large collection of core and user-contributed components that make it easy to implement system adapters (for interfacing with backend systems), data transformations, and sophisticated routing. At present, there are well over 100 different components
#3 Community: The Camel community is second to no other open-source integration framework's community. The message boards are vibrant and lively, new committers are accepted frequently, and many people are actively contributing new components, bug fixes, and general help to newcomers. Among the top criteria for using an open-source project is community, and Camel's is in my opinion the best.
DZone: In a couple sentences, please describe what readers will get from this Refcard.
Christian Posta: I hope users will be able to use the Camel Refcard to quickly figure out how to use and configure Camel components that are indispensable for most integration routes.
DZone: What do you wish we could have included in the Refcard that didn't make it to the final cut? Where else can readers look to get better informed about Camel?
Christian Posta: There are so many great camel components!! It would be awesome to have included more, but here are a few others that may interest readers:
* Flatpack -- for fixed-file formats (think mainframe integration?)
* HDFS -- for Hadoop integration
* jclouds -- cloudy operations
* JDBC -- traditional RDMS
* MINA -- tcp stockets
* Netty -- Nonblocking IO
* SJMS -- "simple" JMS
* SpringIntegration -- bridge existing SI flows
* Twitter -- accessing the twitter API
and more... you have to checkout http://camel.apache.org/components.html for the full list
Time: 2013-01-23 13:00:00
Length: 60 minutes