You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by mmotta <ma...@neogrid.com> on 2008/10/31 20:06:33 UTC
Re: ServiceMix and Application Servers
mmotta wrote:
>
> Hi,
>
> I have the folowing scenario:
>
> 1) +2 millions messages per day (xsl transformation, http endpoits, file
> binding, jdbc)
> 2) High Availability (24x7 cluster by software or hardware)
> 3) Load Balance
> 4) Database conectivity (JDBC)
> 5) Servlet Container (02 applications)
>
> Can only the servicemix handle sucessfully the case above?
>
> Or using servicemix inside a Application Server is a better choice?
>
>
>
--
View this message in context: http://www.nabble.com/ServiceMix-and-J2EE-servers-tp20186721p20272348.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix and Application Servers
Posted by Adrian Trenaman <tr...@progress.com>.
That's about 24 messages per second average? Shouldn't be a problem
for SMX. What's the peak traffic like?
You could put your servlet stuff onto Tomcat, use SMX for your
routing, and then no need for an App Server. Or of course, if you
already have an app server and you're happy with that deployment
architecture you can drop SMX into that.
/Ade
On 31 Oct 2008, at 15:06, mmotta wrote:
>
>
>
> mmotta wrote:
>>
>> Hi,
>>
>> I have the folowing scenario:
>>
>> 1) +2 millions messages per day (xsl transformation, http endpoits,
>> file
>> binding, jdbc)
>> 2) High Availability (24x7 cluster by software or hardware)
>> 3) Load Balance
>> 4) Database conectivity (JDBC)
>> 5) Servlet Container (02 applications)
>>
>> Can only the servicemix handle sucessfully the case above?
>>
>> Or using servicemix inside a Application Server is a better choice?
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/ServiceMix-and-J2EE-servers-tp20186721p20272348.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>