Architecture

HDAP, RadiantOne’s Big Data Directory, is versatile and designed to meet your identity infrastructure needs, now and well into the future. There are two main modes for HDAP deployment, each a different SKU: Active-Passive Mode and Cluster Mode. The directory can be leveraged in a variety of deployment scenarios in conjunction with RadiantOne FID or as a stand-alone LDAP server.

Active-Passive Mode: HDAP Deployed on One Node as a Stand-Alone LDAP Server

The Big Data Directory can be deployed in smaller environments as a single-node, classical LDAP server. In this case, HDAP offers the same quick performance profile as classical LDAP for information lookup (reads), while delivering up to ten times faster throughput for writes. When used in this way, it’s an excellent solution for companies looking to consolidate and migrate away from aging Sun/Oracle/Novell Directory architectures.

Cluster Mode: HDAP Deployed Across Multiple Nodes

When deployed as a cluster, HDAP is highly available and extremely scalable—in fact, you can bring new nodes online in minutes. Cluster sites require a local area network with good connectivity, running at speeds of one gigabit or better. Each site can have one or more clusters deployed. There are two main types of deployment architectures within the cluster framework:

Single Cluster: Add Follower-Only Nodes for Better Throughput

For high availability within a cluster, a minimum of three nodes—each with a replica of the HDAP store—is required, and a load balancer directs client traffic across all cluster nodes. Of the three core nodes, there will always be a single leader node and the rest will be either follower nodes (which could take over if the leader fails) or follower-only nodes.

The status of each node is handled by a distributed configuration manager, which maintains configuration consistency for the cluster. If the leader node fails, a new one will be automatically elected to ensure the integrity of the cluster. The consistency of the directory image across all cluster nodes is addressed with block replication, and any changes to the virtualized data are done on the leader node, then replicated out to the followers.

RadiantOne Big Data DirectoryIn a cluster deployment, changes to the virtualized data are done on the leader node, then replicated out to the followers

Multiple Clusters: Add More Sites with Inter-Cluster Logical Replication

If you have the need for multiple sites—whether that means several data centers or a disaster recovery site—you can deploy multiple clusters. HDAP stores deployed across more than one site can participate in inter-cluster logical replication.

Multi-Cluster

HDAP stores deployed across more than one site can participate in inter-cluster logical replication, so that the data is always up to date

This deployment scenario supports multi-master replication based on the same model that traditional LDAP directories use today, where the current leader node in each cluster is responsible for accepting changes from other clusters. These changes will then be pushed out to other nodes within the cluster through block replication, as shown in the diagram above.

While the Big Data Directory is the default directory storage for RadiantOne FID, you can also use it in any situation where you’d deploy a directory—with significant advantages in performance and scalability:

  • Power your largest portal, Web Access Management, and federation deployments—including CA SSO (SiteMinder), ISAM, and OAM.
  • Deliver quick access to contextual views containing integrated data from across your identity infrastructure to existing applications and the cloud.

RadiantOne FID extracts all the rich user information and contextual data from diverse data stores—SQL, LDAP, and web services—and joins it to create a common, integrated view of each identity. Then HDAP, acting as a highly-scalable context server, stores these materialized views and delivers them at high speed.

Application-specific attributes can be stored at the virtualization layer, without requiring schema extensions to the underlying data stores. RadiantOne FID builds custom hierarchical views from the complete profiles to meet the needs of each application, so that all your applications get the identity they need, in a format they can understand. And RadiantOne FID’s persistent cache with auto refresh feature ensures that profile information is always available and always up to date.

Dig Deeper:

  • Download our HDAP, RadiantOne Big Data Directory, overview paper.