servicemix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache ServiceMix > ServiceMix 5 - NMR Improvements
Date Wed, 02 Mar 2011 21:53:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/2036/9/13/_/styles/combined.css?spaceKey=SM&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">ServiceMix
5 - NMR Improvements</a></h2>
    <h4>Page  <b>added</b> by             <a href="">Gert
    <div class="notificationGreySide">
         <p>This document attempts to capture the requirements, use cases and other
ideas we have in mind for the improved NMR layer inside ServiceMix.</p>

<h3><a name="ServiceMix5-NMRImprovements-Requirements"></a>Requirements</h3>
	<li>Allow for
		<li>low overhead interaction between endpoints on the same node</li>
		<li>transparent interaction between endpoint multiple ServiceMix nodes</li>
	<li>Service Registry
		<li>API to allow looking up services/endpoints on local node</li>
		<li>Extensible to allow adding custom (business-oriented) information in it</li>
	<li>Service Locator
		<li>Allow delegating service invocations to services on remote nodes</li>
	<li>Support using distributed transactions (across components and nodes)
		<li>Using a default transaction manager inside ServiceMix</li>
		<li>Using a external/remote transaction manager</li>
		<li>State replication</li>
		<li>Management of cluster nodes</li>

<h3><a name="ServiceMix5-NMRImprovements-Usecases"></a>Use cases</h3>
	<li><b>Use case 1</b>: Loosely coupled Camel routes on the same node <br
class="atl-forced-newline" /> Camel routes in separate bundles can interact by sending
exchanges through the NMR without the overhead of serialization/copying data/...</li>
	<li><b>Use case 2</b>: Loosely coupled Camel routes on multiple nodes <br
class="atl-forced-newline" /> Camel routes on multiple nodes can communicate by sending
exchanges through the NMR.  The underlying implementation will probably be ActiveMQ Apollo.
 <br class="atl-forced-newline" /> (What data types can we support here?)</li>
	<li><b>Use case 3</b>: Seamlessly migrate Camel routes running on the same
node to different nodes (i.e. without the calling route having to be aware of the change)</li>

<h3><a name="ServiceMix5-NMRImprovements-AnewnamefortheNMR"></a>A new name
for the NMR</h3>
<p>Some suggestions:</p>
	<li>SGL (ServiceMix Gateway Layer)</li>
	<li>SML (ServiceMix Messaging Layer</li>
	<li>EML (Endpoint Messaging Layer)</li>

    <div id="commentsSection" class="wiki-content pageSection">
       <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
       <a href="">View
       <a href=";showCommentArea=true#addcomment">Add

View raw message