Directory Scalability at Telcoms

This is a common theme when I visit our Telcom customers.. Ludo writes..

a wireless telecom operator happily user of Sun Directory Server 5.2 (patch3) with a few tens of million entries.

It is never the Directory that fails to meet our customers requirements, it is usually something in the web application or likely the storage which cause problems for them. The Sun Directory Server scales very well for the type of operations which Wireless carriers require. These are typically read-only types of transactions such as authentication or user profiling.

200702230057

In the above diagram, we can clearly see the effects of horizontal scalability for a telecom. As they need more LDAP read transactions (searches and DN retrievals), they can keep adding Directory Replicas to meet their demand. Load balancers would provide the traffic shaping to spread the traffic across the various replicas.

A limit does however become apparent for the Directory Masters. You can keep adding DIrectory Masters in a horizontal fashion. These peered masters will each have their own Multi-Master Replication (MMR) agreements. Should the type of write transactions become extensive, your Directory will soon start to suffer. In the Directory Server 5.2 (and earlier) releases, you are limited to four Directory Masters.

In the next release of Directory Server 6.0, this limit of four Directory will go away.

Ludo's Sketches Blog

Technorati Tags:

Comments:

Post a Comment:
Comments are closed for this entry.
About

I'll be writing about topics that would interest users and developers of Sun Java Communication Suite.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today