EJB3.1 Remote invocation - is it distributed automatically? is it expensive?

Posted by Hank on Stack Overflow See other posts from Stack Overflow or by Hank
Published on 2010-04-27T16:46:40Z Indexed on 2010/05/05 8:08 UTC
Read the original article Hit count: 253

Filed under:
|
|
|

I'm building a JEE6 application with performance and scalability in the forefront of my mind.

Business logic and JPA2-facade is held in stateless session beans (EJB3.1). As of right now, the SLSBs implement only @Remote-interfaces. When a bean needs to access another bean, it does so via RMI.

My reasoning behind this is the assumption that, once the application runs on a bunch of clustered application servers, the RMI-part allows the execution to be distributed across the whole cluster automagically.

Is that a correct assumption?

I'm fine with dealing with the downsides of that (objects lose entityManager session, pass-by-value), at least I think so. But I am wondering if constant remote invocation isn't adding more load then necessary.

© Stack Overflow or respective owner

Related posts about ejb3

Related posts about jee6