There are two main types of deployment with the Sun OpenDS Standard Edition proxy:
Using load balancing
In order to decide which type of deployment you want, consider this: where and how is your data stored? how much data do you handle?
If all your data is stored on a replicated data store, then use a deployment with load balancing. See Configuration 1: Simple Load Balancing.
If your data is partitioned or you have a large database and want to split your data so that it is partitioned on different data sources, then use a deployment with distribution. See Configuration 2: Simple Distribution.
More complex deployment scenarios can be defined, which layer load balancing and distribution. The main question will be, do you need load balancing, or distribution, or both?
Other than simple load balancing and simple distribution, the following example deployments will be presented:
If you want to deploy data centers in different geographical locations, for example, you could deploy failover between two load-balanced data centers. See Configuration 3: Failover Between Data Centers.
If you want to use distribution but want the data partitions to be replicated, then you can deploy Sun OpenDS Standard Edition proxy using distribution which routes to load balancer. See Configuration 4: Distribution with Load Balancing.
If you want to use distribution with the data partitions replicated, but for availability and disaster recover you want the partitions to not only be replicated in one data center but also want to replicate the data centers in two different geographical locations, then you could deploy an architecture similar to Configuration 5: Distribution with Failover Between Data Centers.
You can add a global index catalog to deployments using distribution, to map entries to a specific partition. This will help minimize the use of broadcasts. For information on configuring a global index catalog, see Configuring the Global Index in Sun OpenDS Standard Edition 2.2 Administration Guide.