It is important not to expose the client to the complexity of using these fine-grained BOs. Frequent access to a large set of fine‐grained components greatly increases the complexity of BOs control. Transaction-control, security-management, and service-lookup are all examples of this complexity.

Like the GoF façade pattern, the use of a coarse-grained layer in JEE decreases the coupling between the client and the business components represented by BOs of fine granularity (and we can think of a Session Façade as an extension of the GoF façade pattern in JEE). The Session Façade pattern represents this coarse-grained layer. An architecture built with the Session Façade provides a facade of more generic (or coarse-grained) methods for clients. The two biggest benefits of using the Session Façade pattern are as follows:

• It does not expose the high complexity of the business objects (BOs) and their relationships. 
• It decreases network traffic. This occurs because remote calls are limited to coarse-grained methods exposed by Session Façade instead of the fine-grained business objects.

Of course, EJB remote calling was used much more in the old JEE scenario in comparison to current architectures. It is important that this is taken into consideration.