* Support of one-to-one scheme of remoting (similar to the one currently supported by Spring);
* Support of one-to-many scheme of remoting, which assumes that one client selects remote service for invocation from one of predefined locations;
* Support of one-to-many scheme of remoting with dynamic discovering of remote services;
* Several built-in policies for selecting remote service for invocation are included (they are applied if service is available in several locations);
* Built-in functionality for handling remoting exceptions of method invocations that provides ability to re-invoke remote service using different service location automatically;
* Steep learning curve since ideological implementation of Cluster4Spring bears a close resemblance to the implementation of remoting in Spring;
* Non-intrusive for existing applications - it is simply enough to change appropriate remoting-related Spring configuration files to start using Cluster4Spring;
* Provides a convenient way to add custom interceptors both on client and server side;
* Flexible and modular architecture which is ready for further extensions and customizations;
* Library is stable and ready to use;