[CONF] Apache Camel: Hiding Middleware (page edited)

[confluence]

Page Edited : CAMEL : Hiding Middleware Hiding Middleware has been edited by James Strachan (Aug 11, 2008). (View changes) Content: When writing software these days, its important to try and decouple as much middleware code from your business logic as possible. This provides a number of benefits... you can choose the right middleware solution for your deployment and switch at any time you don't have to spend a large amount of time learning the specifics of any particular technology, whether its JMS or JavaSpace or Hibernate or JPA or iBatis whatever For example if you want to implement some kind of message passing, remoting, reliable load balancing or asynchronous processing in your application we recommend you use Camel annotations to bind your services and business logic to Camel Components which means you can then easily switch between things like in JVM messaging with SEDA using JMS via ActiveMQ or other JMS providers for reliable load balancing, grid or publish and subscribe for low volume, but easier administration since you're probably already using a database you could use Hibernate or JPA to use an entity bean / table as a queue iBatis to work with SQL JDBC for raw SQL access use JavaSpace

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences