JavaCamp II : DB and ESB

The second edition of Octo‘s Barcamp Java was great. This event format is really interesting because it allows having the opinions of others, learn through their experience and meet interesting people.
Two of my proposals were adopted: RDF+OWL and database.
The subject RDF+OWL has not really been interested and has finished in the more generally REST subject. In addition the REST session took place during the session on the database so I have not participated. I re-suggest it next time, with another title these acronyms were not always known.
What database for what need ? it was the question on which I wanted to talked about. 8 votes have allowed this matter to be debated in a room. But finally 4 responded to the call. The exchange has not been less interesting. This will be the subject of my next post.
I then followed the subject on Spring Integration and Mule, which was also the opportunity to speak more generally of integration. I just give you a list of tools mentioned (I make comments on what I know):

  • Spring integration : Version 1.0 have been released, this framework is the implementation of the design pattern book EAI Pattern.
  • JitterBit : an open source EAI with advanced management tool, the GUI is attractive but I have not had time yet to really test the product
  • OpenAdaptor : First opensource EAI developed by a german team. I personally used to develop an EAI dedicated to health which actually interconnects the SAMU of the Champagne-Ardennes region (3 to 4 messages per minute it’s still reasonable). The product is stable and multi-source design, pipe, sink is well thought out. There is a lot of connectors but not always reusable, it is better to re-develop your own when you have specific features. I used the original version 1.7.2, there was no version 2 but a complete refactoring that is now version 3. An article by the author was published recently in JDJ.
  • Mule : a lightweight ESB now well known, I have not had the opportunity to implement it, but before the arrival of Spring Integration it was one that interested me most. Nicolas has implemented it and has even made a quickie at DEVOXX08.
  • OpenESB : implementation of the Sun JBI specification (JSR-208) dedicated to integration
  • JBoss ESB : ESB by JBoss
  • Apache Synapse : lightweight ESB of Apache Foundation
  • Apache serviceMix : ESB, JBI implementation
  • Apache CAMEL : implementation of EAI pattern (idem Spring integration)
  • Apache CXF : implementation of JAX-WS.
  • Axis2 : same but with asynchronous mode and REST. I started working on web services with version 1 of this framework and realize practical training works with it. The architecture allows flexible configuration based on a chain between the request and response. It is simple to use to make an ETL. Version 2 provides asynchronous, more performance and AXIOM to manage attachments (easier to use than SwA)
  • APMQ : the new specification to standarize messaging tools (initiated by JBoss), it is only the beginning but we have to follow
  • ActiveMQ : the open source open source MQ, Julien Dubois has some experience on the subject and tells us that we must be wary of some bugged versions (5.0 for example). The tool is not mature and often encounter problems because developers believe they can integrate easily in their application. Apparently this is not as simple as a single jar to add.
  • OpenMQ : the Sun open source MQ, I could follow the session at the DEVOXX08, it was very broad but Sun show that the project is well supported and adopted by their clients. If I switch to open source (currently i use WebSphere MQ) i think i choose this one.
  • WebSphere MQ : the historical MQ from IBM that I use now. Robust, mature but hard to configure. Even if IBM provide RCP application for configuration it remains complex. I added the MQ Everyplace module to deploy on mobile handsets, configuration is even more complex. Once it is ready it works well.

Thanks to Luc Bizeul who organize this event and also for the cocktail at the end. I’m waiting for the next 😉

Une réflexion sur « JavaCamp II : DB and ESB »

  1. NB : i make a mistake, Julien never said that ActiveMQ is not mature. The tool is mature and actually in production in many enterprises. But certain versions are bad, normally all after 5.1 is now correct, and the tool have to be administrated in production.

Les commentaires sont fermés.