Yes, if you use this then it is no longer necessary to use apache as a load balancer. <br><br>There are a few advantages to using Wildfly, namely:<div><br></div><div>- Front and back end servers are all Wildfly, allowing them to all be managed uniformly through domain mode (which also means pure Java, so no native bits)</div><div>- Undertow should be able to perform better than apache as a load balancer (although we don&#39;t have any firm benchmarks for this yet), and will be able to use new protocols such as HTTP2 to communicate with backend servers which are more efficient on the wire. </div><div><br></div><div>The down side is of course that apache is already widely deployed, so a lot of organisations will already have experience with it, or be using apache for other things as well. </div><div><br></div><div>Stuart<br><div><br></div></div><br><div class="gmail_quote">On Tue Jan 13 2015 at 2:35:26 PM Jorge Solórzano &lt;<a href="mailto:jorsol@gmail.com">jorsol@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hi Stuart,</p>
<p dir="ltr">This means is no longer necessary to use Apache httpd as front end? What should be the pros and cont. when used like this?</p>
<div class="gmail_quote">El ene 12, 2015 8:48 PM, &quot;Stuart Douglas&quot; &lt;<a href="mailto:stuart.w.douglas@gmail.com" target="_blank">stuart.w.douglas@gmail.com</a>&gt; escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi everyone,<div><br></div><div>A while ago we added support to Wildfly to allow it to be used as a front end mod_cluster based load balancer. </div><div><br></div><div>I am going to blog about this once it appears in a released version, but for now if anyone wants to try it out I have an example in my github at <a href="https://github.com/stuartwdouglas/modcluster-example" target="_blank">https://github.com/stuartwdouglas/modcluster-example</a> </div><div><br></div><div>The example basically contains the CLI commands need to start a domain with two backend servers and a front end load balancer (with a simple deployment that prints the server name that handles the request, and can start counting requests to demonstrate sticky sessions and failover), although the deployment path and local IP address will need to be modified appropriately. </div><div><br></div><div>I&#39;m just posting about this here in case it is interesting to anyone, as it should provide a very simple way to get started with clustering. </div><div><br></div><div>Stuart</div>
<br></blockquote></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br></blockquote></div>
</blockquote></div>