camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Camel > clustering and loadbalancing
Date Fri, 26 Feb 2010 12:13:00 GMT
<html>
<head>
    <base href="http://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/1519/1/1/_/styles/combined.css?spaceKey=CAMEL&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background-color: white" bgcolor="white">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
     <h2><a href="http://cwiki.apache.org/confluence/display/CAMEL/clustering+and+loadbalancing">clustering
and loadbalancing</a></h2>
     <h4>Page <b>edited</b> by             <a href="http://cwiki.apache.org/confluence/display/~cmoulliard">charles
Moulliard</a>
    </h4>
     
          <br/>
     <div class="notificationGreySide">
         <p>Camel proposes different solutions to allow your solution to be scalable,
to distribute the load between different instances. The choice will depend on how you will
deploy/package Camel (standalone mode, embedded in a J2EE or OSGI server, ...) and how the
servers will be configured (master/slave, ...).</p>

<h2><a name="clusteringandloadbalancing-Loadbalancing"></a>Loadbalancing</h2>

<p>This approach allows to distribute the load between different endpoints. The from
endpoint plays the role of a 'proxy' when we use by example a jetty server</p>

<p><a href="/confluence/pages/createpage.action?spaceKey=CAMEL&amp;title=load-balancer.html&amp;linkCreation=true&amp;fromPageId=14483461"
class="createlink">loadbalance()</a></p>

<h2><a name="clusteringandloadbalancing-Clustering"></a>Clustering</h2>

<p>The clustering can be achieved in different ways : Work distribution, Consumer competition,
... depending how you would like to configure your infrastructure (one or several instances
running on the same machine or distribute across a cloud of servers).</p>

<ul>
	<li>Same JVM &amp; CamelContext</li>
</ul>


<p>Different Camel components can be used depending if the work must be done in a sync
or async way</p>

<ul>
	<li>
	<ul>
		<li>Without persistence</li>
	</ul>
	</li>
</ul>


<p>Async : <a href="/confluence/display/CAMEL/SEDA" title="SEDA">seda://</a>
+ threads()</p>

<p>Sync : <a href="/confluence/display/CAMEL/Direct" title="Direct">direct://</a>
+ threads()</p>


<ul>
	<li>
	<ul>
		<li>With persistence</li>
	</ul>
	</li>
</ul>


<p>JMS queue engine : <a href="/confluence/display/CAMEL/JMS" title="JMS">jms://</a>
+ threads()<br/>
Activemq queue engine : <a href="/confluence/display/CAMEL/ActiveMQ" title="ActiveMQ">activemq://</a>
+ threads()</p>

<ul>
	<li>Different JVM &amp; CamelContext</li>
</ul>


<p>When the infrastructure offers the possibility to deploy the application on several
machines, then you can use the approaches presented at point 2.1. That means means that you
will deploy the same application on several nodes and in this case, we have competitor consumers.
Depending on the load on the servers, messages can be consume by application 1 running on
Server 1 instead of application 2 running on Server 2. If you prefer to deploy routes on different
servers having different CPU/memory, then you can use the following components</p>

<ul>
	<li>
	<ul>
		<li>Suitable for solutions running in standalone mode or deployed in Web Application
Server (different WAR/EAR)</li>
	</ul>
	</li>
</ul>


<p><a href="/confluence/display/CAMEL/VM" title="VM">vm://</a></p>

<p>This component cannot be used between different OSGI servers</p>

<ul>
	<li>
	<ul>
		<li>Between different instances of OSGI servers (SMX4)</li>
	</ul>
	</li>
</ul>


<p><a href="/confluence/display/CAMEL/NMR" title="NMR">nmr://</a></p>

<p>Camel can be not only plugged on the NMR bus but can also use the clustering functionality
offered by ServiceMix 4 ()</p>

<h2><a name="clusteringandloadbalancing-Cloudcomputing"></a>Cloudcomputing</h2>

<ul>
	<li>Cassandra<br/>
It could be interesting to create a Cassandra endpoint to allow to consume<br/>
info/camel messages from Cassandra DB (NOSQL database) or to push there<br/>
camel message (using id + binary stream). It might also make an interesting<br/>
aggregator implementation since its also distributed &amp; can support multi-master</li>
</ul>


<ul>
	<li>Camel-terracotta<br/>
Extends the SEDA component</li>
</ul>

     </div>
     <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href="http://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
       </div>

       <a href="http://cwiki.apache.org/confluence/display/CAMEL/clustering+and+loadbalancing">View
Online</a>
       |
       <a href="http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=14483461&revisedVersion=6&originalVersion=5">View
Change</a>
              |
       <a href="http://cwiki.apache.org/confluence/display/CAMEL/clustering+and+loadbalancing?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message