Minimizing Remote Calls
The primary performance concern associated with a distributed architecture such as EJB is the amount of network traffic it requires. When a remote client makes a call to an EJB there’s a certain amount of overhead involved. Part of this is just the time it takes to move data between the client and the container across the network. You also have the impact of the transaction and security processing that takes place when the container receives a client request. You can’t get away from this overhead completely because it’s part of the price you pay for the benefits of a distributed application. However, you should be conscious of the number of calls a remote client is required to make to do its work. As you’ve seen in earlier ...
Get Special Edition Using Enterprise JavaBeans™ 2.0 now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.