Skip Navigation Links | |
Exit Print View | |
Oracle Directory Server Enterprise Edition Deployment Planning Guide 11g Release 1 (11.1.1.5.0) |
Part I Overview of Deployment Planning for Directory Server Enterprise Edition
1. Introduction to Deployment Planning for Directory Server Enterprise Edition
2. Business Analysis for Directory Server Enterprise Edition
Part II Technical Requirements
3. Usage Analysis for Directory Server Enterprise Edition
4. Defining Data Characteristics
5. Defining Service Level Agreements
6. Tuning System Characteristics and Hardware Sizing
7. Identifying Security Requirements
8. Identifying Administration and Monitoring Requirements
9. Designing a Basic Deployment
Using Load Balancing for Read Scalability
Using Replication for Load Balancing
Assessing Initial Replication Requirements
Load Balancing With Multi-Master Replication in a Single Data Center
Load Balancing With Replication in Large Deployments
Using Server Groups to Simplify Multi-Master Topologies
Using Directory Proxy Server for Load Balancing
Using Distribution for Write Scalability
Using Directory Proxy Server for Distribution
Routing Based on a Custom Algorithm
Using Directory Proxy Server to Distribute Requests Based on Bind DN
Distributing Data Lower Down in a DIT
Logical View of Distributed Data
Directory Server Configuration for Sample Distribution Scenario
Directory Proxy Server Configuration for Sample Distribution Scenario
Considerations for Data Growth
Using Referrals For Distribution
Using Directory Proxy Server With Referrals
11. Designing a Global Deployment
12. Designing a Highly Available Deployment
Part IV Advanced Deployment Topics
13. Using LDAP-Based Naming With Solaris
14. Deploying a Virtual Directory
The basic deployment described in Chapter 9, Designing a Basic Deployment assumes that a single Directory Server is enough to satisfy the read and write requirements of your organization. Organizations that have large read or write requirements, that is, several clients attempting to access directory data simultaneously, need to use a scaled deployment.
Generally, the number of searches a Directory Server instance can perform per second is directly related to the number and speed of the server's CPUs, provided there is sufficient memory to cache all data. Horizontal read scalability can be achieved by spreading the load across more than one server. This usually means providing additional copies of the data so that clients can read the data from more than one source.
Write operations do not scale horizontally because a write operation to a master server results in a write operation to every replica. The only way to scale write operations horizontally is to split the directory data among multiple databases and place those databases on different servers.
This chapter describes the different ways of scaling a Directory Server Enterprise Edition deployment to handle more reads and writes. The chapter covers the following topics: