1. Features

c-treeACE offers support for the following features:

• ACID-compliant transactions
• Disk-based and memory files controlled at the file level
• Configurable data and index cache sizes
• Automatic disaster recovery
• Data Camouflage
• Partitioned files
• Realtime/Hot backups
• Replication API
• Stored procedures, triggers, and user defined functions
• Concurrent SQL and record-oriented ISAM access
• Graphical administrative tools and utilities
• Immediate consistency

2. APIs

c-treeACE has a layered system architecture with different application programming interfaces (APIs) available to the developer at each layer. The lower layers have proprietary APIs that allow more direct control of data and index manipulation at the expense of added complexity whereas higher layers offer more industry standard APIs but may offer less precise control. Software developers can choose to use one API for the application or use multiple APIs concurrently.^[1]

Underpinning c-treeACE is an ISAM engine. Developers can use a native C API to access the engine directly. Because the ISAM API can be used to create applications with non-relational data structures, c-treeACE can be included as part of the NoSQL class of databases.^[2] Here, because the software can also be used to create databases that are in fact SQL/relational (particularly with the SQL layer discussed below), NoSQL would refer to a database offering "Not Only SQL" rather than one that excludes SQL.^[3]

The next layer up is what FairCom terms the 'c-treeDB' layer. Interfaces at this layer include C and C++ APIs, VCL components for use with Delphi and C++Builder, and .NET components.

Finally there is an optional SQL layer that allows SQL-92 compliant access to the database engine. At this layer, there are multiple API choices including an ADO.NET data provider, Type 4 JDBC driver, ODBC driver, PHP interface, DbExpress driver for Delphi and C++ Builder. Stored procedures—written in Java for cross-platform portability—are included at the SQL layer.

3. Architecture Choices

c-treeACE includes several different architectures or operational models for developers to choose from.^[4]

3.1. Client/server Model

The client/server model available with c-treeACE uses a typical client/server database architecture. The client-side libraries are compiled into the application and then communicate with the server component (identified as the c-treeACE Server in FairCom parlance). The c-treeACE Express package that FairCom makes freely available for development via its web site supports only this model. FairCom offers licenses to the server component for both ISAM servers (supporting the ISAM and c-treeDB APIs) and SQL servers (supporting all APIs, including SQL).

3.2. Embedded Server

This model is the same as the client/server model above, but the entire server engine can be dynamically linked directly with the application. When practical, this approach can be beneficial by avoiding interprocess communication between the client and server. The communication instead takes place across the stack.

3.3. Standalone

In the standalone models, there is no separate server process to which applications communicate. Instead, a standalone library is built using c-treeACE and linked to the application. Data management operations are performed via one of the record-oriented APIs which then use the native runtime library routines.

Both single user and multiuser libraries can be built with c-treeACE. The multiuser support is a shared-file mode implementation where the operating system provides the locking rather than the server process. Resource contention can become an issue with the standalone multiuser model as concurrency requirements and network operations increase.

The features available with these models are significantly limited as compared to the client/server model. Neither the single user nor multiuser standalone models support SQL APIs, stored procedures, triggers, user defined functions, replication, realtime backup, automatic recovery, encryption,^[5] memory files, or partitioned files. Although there is support for transaction processing and data/index caching with the single user libraries, there is no support with the multiuser libraries..

3.4. Hybrid

A hybrid model exists that FairCom calls LOCLIB which allows a client to perform both local data storage via a standalone library as well as client/server access.

4. Platforms

c-treeACE natively supports the following operating systems:^[6]

• Windows
• Linux
• Solaris
• AIX
• HP-UX
• Mac OS X
• QNX
• FreeBSD
• NetBSD
• NetWare
• SCO OpenServer

5. History

The product was originally developed by Dr. William Fairman^[7] and released as the 'c-tree File Handler' in 1984. The name originated from the fact that c-tree was an implementation of a B+ tree written for the then burgeoning microcomputer market in the C programming language.

The original client/server architecture was introduced in 1987.^[8] At that time, the client/server version supported only the ISAM API. The c-tree DB and SQL APIs were introduced later, in 2003.^[9]

The product underwent a name change in 1990 with the release of 'c-tree Plus' version 6 and then again in 2008 with the release of 'c-treeACE' (Advanced Core Engine) version 9. Along with the name change in 2008 came the release of 'c-treeACE Express'.^[10]

c-treeACE now spans over 100 countries on four continents, including utilization by 43% of Fortune 100 companies.^[11]

The content is sourced from: https://handwiki.org/wiki/Software:C-treeACE