The standard client/server model supports the complete FairCom DB API in the form of inter-process communication requests made to the FairCom Server. Instead of linking with a FairCom DB engine performing direct file I/O, the application is linked with a FairCom DB communication library making network requests to the FairCom Server. Select the desired communication protocol for your application when building the FairCom DB client-side library.
A wide selection of protocols is available, including TCP/IP, IPX/SPX, Shared Memory, and a number of proprietary protocols. No network programming experience is required. In most cases, converting from stand-alone model to client/server is as simple as re-linking the FairCom DB application. Heterogeneous support allows clients of various architectures to talk to a FairCom Server at the same time, making this model a strong network database solution.
Benefits
All disk I/O is done by the FairCom Server, taking full advantage of data/index caches and minimizing network traffic for maximum performance.
Client libraries resolve the complete FairCom DB API, allowing standalone applications to move to client/server seamlessly.
Transaction processing with full roll-forward, rollback, auto-recovery and unique transaction history feature.
Heterogeneous support: For example, SPARC/Intel clients can share data across any combination of client/server platforms. Connect any client to any Server.
Scalability. Large number of supported platforms.
Complete client-side library source code included in the FairCom DB package. Easy platform migration.
Heavily dynamic indexes are automatically maintained for optimal speed and size, eliminating the need for routine rebuilding.
Consideration
Consider migrating applications using the FairCom DB low-level API to the FairCom DB ISAM API. The ISAM API requires less network traffic and includes batch operations to reduce network traffic, boosting performance.
