Topography - how does it fit into your infrastructure
A distributed application The DataFrameworks software is a distributed application consisting of a number of basic components. It logically resides between the ‘Clients’ and the ‘Storage’. Implementing this application is ‘no risk’ as it may be installed and removed without any lasting effect on the system. Clients The Client is simply any machine that utilizes the DataFrameworks interfaces, GUI or CLUI, to interact with the other DataFrameworks components. Each Client machine will have its own installation of the DataFrameworks ‘Client' component. Alternatively it will utilize a network accessible installation for easier upgrade and maintenance. Main server The ‘Main Server’ daemon process runs on a dedicated machine that houses the DataFrameworks database. It acts as a TCP/IP hop for all the Clients to execute DataFrameworks related file system commands on the File Server(s). File server DataFrameworks has a ‘File Server’ component and runs a File Server daemon process. It is responsible for executing the create directory, delete directory, and stat directory commands requested by the Client(s) or Main Server. This component runs on any machine that has partitions mounted to it (either locally or over a network) on which DataFrameworks must manage data. Data Portal The Data Portal component is simply a File Server with the additional responsibility of maintaining the Data Portal Tree. The Data Portal Tree is DataFrameworks’ global name space implementation. Does it easily fit into your existing infrastructure? DataFrameworks is designed to layer on top of your existing file systems and below the existing application infrastructure to implement data management “best practices.” The implementation of DataFrameworks is virtually “no risk,” as it can be completely removed, and the company is simply left with better organized file systems. Click here for more information.