RadiantOne VDS is a high-performance LDAP v3 directory service. Identity data is delivered to various services such as web portals and applications that require high-availability and the performance of an LDAP directory server.
In dynamic access mode, RadiantOne VDS can deliver data with up to 95% of the speed of the underlying source. When the underlying source's performance and availability is high, VDS delivers data quickly and efficiently with no performance enhancements necessary.
RadiantOne VDS can also cache information (persistent or memory), for scenarios that require guaranteed high speed and enhanced performance for data delivery.
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 can be configured within the VDS by entry or by query depending on the complexity of the view designed and 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.
RadiantOne persistent caching technology enables the system to deliver data, independent of the data source, therefore performing at the level of any LDAP v3 directory service.
All objects and values in the selected virtual view are cached into the local LDAP repository. The cache ensures high performance and availability of the directory. The underlying source is no longer a performance constraint.
Persistent cache can be refreshed in several ways.
- 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 automatically be refreshed.
- 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.
Back to top ^ |
