Sometimes, query speed requirements can be higher than the underlying source can deliver. RadiantOne provides a number of performance-enhancing options that enable VDS to respond faster to LDAP operations. These options allow you to deploy with the best possible balance of performance, scalability, and data relevance.

Depending on the type, volume and volatility of the queries, memory and/or persistent cache can be deployed.

RadiantOne offers caching refresh mechanisms to match your application needs with your data source: Time To Live (TTL), Changelog, Database Trigger (by event notification), or by Periodic Query.

Memory Cache is configured within the VDS by entry or by query, depending on the performance enhancement needs of the individual data source.

Query memory cache: Used for frequent repetitious queries, such as frequently requested profiles / user account information. If the same query is made within the TTL, the query is returned from the memory cache instead of the underlying source.

Entry memory cache: Object attributes and values are cached as queries are made. If another request is made for the same entry within the TTL, the information is returned from the memory cache instead of the underlying source.

Persistent cache: Enables the system to deliver data, independent of the original data source's performance. Render and persist data modeled virtual views to give you the highest level of performance available in the industry, equal to any LDAP v3 compliant server. Query performance is no longer constrained by complex joins and searches across multiple data sources. 

Persistent Cache offers:

• The highest response and query speeds, equal to standard v3 LDAP Directory Servers.
• Scalability across multiple servers and VDS instances.
• Faster recovery from server failure, since there is no re-build of the cache.
• Lower loads on backed sources.
• Incremental, real-time updates of the cache image by detecting changes in the backend sources.
• Guaranteed delivery of cache updates leveraging an enterprise service bus (ESB).

 

Persistent Cache Refresh: Event-driven cache refresh technology means low latency and real-time cache updates. Connectors monitor changes at the sources level and send incremental updates to the cache image as needed. This lowers load on back-end sources, and enables faster access rates at the VDS level.

VDS Context Edition understands and manages object relationships, propagating the right event to the right contextual view. Updates through VDS are routed to the appropriate backend source(s), and when the update is validated, the cache is then updated to always reflect the reality of the backend source only. This differs significantly from other traditional synchronization solutions, where update are designed around a point-to-point or hub and spoke pattern. RadiantOne cache refresh leverages a ESB/JMS to guarantee delivery of updates, and only when updates are delivered, verified, and processed, is the change made to the persistent cache.

If the VDS receives an update for information that is stored in cache, the underlying data source(s) will receive the update, and the persistent cache will be refreshed automatically . If a change occurs at the data source level, connectors will detect the change and propagate it into the persistent cache. This functionality ensures real-time data integrity at the VDS level at all times. Persistent cache can also be refreshed periodically, mimicking an ETL process.

Backend Sources: RadiantOne VDS automatically detects failures in backend sources and will re-route operations to alternate specified servers. Any change in status of connected resources are logged and service alerts are emailed to alert administrators. 

VDS Failover: RadiantOne comes with tools that allow you to set up redundant VDS systems for failover in the case of a server failure. The RadiantOne Access Router will detect the failure and automatically switch over to another VDS instance.

For more fail-over options, see RadiantOne Access Router.

VDS REPLICATION

RadiantOne VDS has built-in instance replication. VDS configuration and local store data is automatically replicated into multiple instances for failover, fault-tolerance, and increased availability in distributed systems.

LOAD BALANCING

RadiantOne VDS includes the RadiantOne LDAP Access Router.  This software-based router monitors connected resources and can be configured for customized load-balancing scenarios.  By providing load balancing at the VDS access level, and backend sources, RadiantOne is able to provide the highest level of performance and availability, scalable to any environment.