I'm new to JBI and ServiceMIx, but looking into it with great interest... however performance is an issue in the system I'm architecting and looking around the net I see that ServiceMix is fast, but not ammazingly fast.
Typical deployments of the system I develop will contain choices on which components to group together on the same node, to improve performance and tradeoff with resource usage. Other middlewares, such as CORBA, provides performance optimizations by detecting collocations (i.e. that a consumer and a provider is running in the same component server / process). In this case the midleware will automatically replace any remote calls with a direct call, thereby removing the overhead of writing to and reading from the transport. Why doesn't ServiceSix do the same? I see that JBI even directly mention that two component instances will always run in separate processes. Why force this? I know; I can write a wrapper of the ServiceMix API myself and handle it. But I was thinking that there must be an excellent reason why this is not already done... or? -- View this message in context: http://www.nabble.com/Performance-Optimization-through-Collocation-tp20152693p20152693.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
