should-i-deploy-the-broker-inside-my-jvm-or-appserver.xml - activemq-web - Git at Google

 <div class="wiki-content maincontent"><p>You can deploy the ActiveMQ Broker inside your JVM or Application Server. Whether you do or not has pros and cons depending on how many JVMs you have and what your backup &amp; recovery policy is.</p>

 <h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-Advantagesofembeddingthebroker">Advantages of embedding the broker</h3>

 <ul><li>embedding a broker means you can use the VM transport which avoids the use of sockets and serialization. Instead ActiveMQ can pass around messages by value.
 	<ul><li>the slight exception to this is ObjectMessage; the JMS specification says you must serialize the body of the ObjectMessage whenever you send it. However you can <a shape="rect" href="how-should-i-use-the-vm-transport.xml">disable this feature</a> if you want really high performance when using VM transport</li></ul>
 	</li><li>its only 1 single deployment unit/JVM rather than 2 coupled processes.</li></ul>


 <h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-Disadvantagesofembeddingthebroker">Disadvantages of embedding the broker</h3>

 <p>If you have lots of JVMs (say 100s of them) and have very stringent requirements; you don't ever want to loose a message and so you want to backup and manage the persistent ActiveMQ database (and/or files) very carefully.</p>

 <p>Having an embdded broker inside each JVM could result in large number of sets of files to manage. So it may be simpler to separate the two out, so that your 100s of JVMs talk to a relatively small cluster of brokers (say 2-10 of them) so that you can avoid worrying about persistent state in each JVM and just focus on backing up and managing the files/databases used by the brokers.</p>

 <p>Also its typically easier to run and manage ActiveMQ brokers when they are separate; you can have some ClassLoader issues when trying to embed ActiveMQ inside an application server. e.g. you can sometimes get <a shape="rect" href="javalangnosuchmethoderror.xml">ClassPath Errors </a></p>

 <h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-See">See</h3>

 <ul><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li><li><a shape="rect" href="run-broker.xml">Run Broker</a></li></ul></div>
	<div class="wiki-content maincontent"><p>You can deploy the ActiveMQ Broker inside your JVM or Application Server. Whether you do or not has pros and cons depending on how many JVMs you have and what your backup & recovery policy is.</p>

	<h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-Advantagesofembeddingthebroker">Advantages of embedding the broker</h3>

	<ul><li>embedding a broker means you can use the VM transport which avoids the use of sockets and serialization. Instead ActiveMQ can pass around messages by value.
	<ul><li>the slight exception to this is ObjectMessage; the JMS specification says you must serialize the body of the ObjectMessage whenever you send it. However you can <a shape="rect" href="how-should-i-use-the-vm-transport.xml">disable this feature</a> if you want really high performance when using VM transport</li></ul>
	</li><li>its only 1 single deployment unit/JVM rather than 2 coupled processes.</li></ul>


	<h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-Disadvantagesofembeddingthebroker">Disadvantages of embedding the broker</h3>

	<p>If you have lots of JVMs (say 100s of them) and have very stringent requirements; you don't ever want to loose a message and so you want to backup and manage the persistent ActiveMQ database (and/or files) very carefully.</p>

	<p>Having an embdded broker inside each JVM could result in large number of sets of files to manage. So it may be simpler to separate the two out, so that your 100s of JVMs talk to a relatively small cluster of brokers (say 2-10 of them) so that you can avoid worrying about persistent state in each JVM and just focus on backing up and managing the files/databases used by the brokers.</p>

	<p>Also its typically easier to run and manage ActiveMQ brokers when they are separate; you can have some ClassLoader issues when trying to embed ActiveMQ inside an application server. e.g. you can sometimes get <a shape="rect" href="javalangnosuchmethoderror.xml">ClassPath Errors </a></p>

	<h3 id="ShouldIdeploythebrokerinsidemyJVMorAppServer-See">See</h3>

	<ul><li><a shape="rect" href="how-do-i-embed-a-broker-inside-a-connection.xml">How do I embed a Broker inside a Connection</a></li><li><a shape="rect" href="run-broker.xml">Run Broker</a></li></ul></div>