c-treeACE
| Developer(s) | FairCom Corporation |
|---|---|
| Initial release | 1984 |
| Stable release | V11.5
/ November 2017 |
| Written in | C, C++ |
| Engine | |
| Type | RDBMS, NoSQL, SQL |
| License | Freemium registerware |
| Website | faircom |
Search C-treeACE on Amazon.
c-treeACE is a database engine developed by FairCom Corporation.[1] The DB-Engines Ranking website classifies c-treeACE as a multimodel database.[2] Software developers typically embed the c-treeACE engine within the applications that they create and then deploy the application and engine together as an integrated solution. The most recent edition is c-treeACE V11.5, which was released in November 2017.[3]
At its core, c-treeACE uses a record-oriented, Indexed Sequential Access Method (ISAM) structure offering high speed indexing mechanisms over those files. Developers can use these direct access methods to design the data and index structures that closely parallel the needs of their application. This paradigm is sometimes referred to as an application-specific database[4] or an embedded database because of the tightly coupled nature of the application and database.
The nature of c-treeACE allows it to be used in a range of products including: embedded systems that require limited disk and memory footprint and silent operation; shrink-wrap products developed by ISVs that require cross-platform support, minimal maintenance, and mass deployment; and enterprise systems that depend on performance and more precision control of database operations than a traditional enterprise database offers.
Two versions of the product are available. c-treeACE Express is freely available for development from FairCom's web site and supports only the client/server architecture. The client-side libraries are precompiled, making it easy to use for evaluation. c-treeACE Professional is licensed separately and supports all architectures and includes full source code for the client libraries and much of the source code for the server.
c-treeACE is one of few databases that specialize in making data locked into legacy database architecture available to modern APIs while minimizing time, resources and risks involved in modernization projects.[5]
c-treeACE combines the benefits of NoSQL such as high performance, low latency and precise data access control, with the flexbility of SQL interfaces.[6]
Features[edit]
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
APIs[edit]
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.[7]
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.[8] [9] 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.[10]
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.
Architecture choices[edit]
c-treeACE includes several different architectures or operational models for developers to choose from.[11]
Client/server model[edit]
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).
Embedded server[edit]
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.
Standalone[edit]
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,[12] 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..
Hybrid[edit]
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.
Platforms[edit]
c-treeACE natively supports the following operating systems:[13]
History[edit]
The product was originally developed by Dr. William Fairman[14] 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.[15] At that time, the client/server version supported only the ISAM API. The c-tree DB and SQL APIs were introduced later, in 2003.[16]
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'.[17]
c-treeACE now spans over 100 countries on four continents, including utilization by 43% of Fortune 100 companies.[18]
In June 2018, FairCom announced the release of the c-treeEDGE IoT Database. c-treeEDGE is powered by the core engine of c-treeACE but is designed specifically for use in edge computing. [19] Then in September, it was announced that c-treeACE had won the Verizon Intelligent Network Control Platform Transaction Server Migration – In-Memory Database solicitation. [2]
References[edit]
- ↑ Adrian Binstock, Dr.Dobb's Journal."/ FairCom c-treeACE Aims To Bridge Both SQL and NoSQL."14 November 2012. Retrieved 13 June 2014.
- ↑ "DB-Engines Ranking". DB-Engines. Retrieved 2018-11-01.
- ↑ SD Times."/ FairCom releases latest version of c-treeACE database software Retrieved 30 November 2017.
- ↑ "Application-Specific Databases". SD. SD Times. Retrieved 25 August 2011.
- ↑ Desire Athow, TechRadar Pro."/ Do I need NoSQL, SQL or both?."22 May 2014. Retrieved 13 June 2014.
- ↑ Lisa Morgan, SD Times."/ Number of NoSQL options grows." 25 March 2014. Retrieved 13 June 2014.
- ↑ "FairCom Marries Speed of ISAM With Standard SQL". SD Times. Retrieved 2011-08-25.
- ↑ Adrian Binstock, Dr.Dobb's Journal."/ FairCom c-treeACE Aims To Bridge Both SQL and NoSQL."14 November 2012. Retrieved 13 June 2014.
- ↑ Raj, Pethuru, Raman, Anupama Handbook of Research on Cloud and Fog Computing Infrastructures for Data Science "[1]. "2018. Retrieved 16 November 2018.
- ↑ Lisa Morgan, SD Times."/ Number of NoSQL options grows." 25 March 2014. Retrieved 13 June 2014.
- ↑ "c-treeACE Professional Operational Models". FairCom. Retrieved 2011-08-25.
- ↑ See https://en.wikipedia.org/wiki/Dentrix#Dentrix_vulnerabilities for Encryption vs Data Camouflage discussion
- ↑ Desire Athow, TechRadar Pro."/ Do I need NoSQL, SQL or both?."22 May 2014. Retrieved 13 June 2014.
- ↑ "Outstanding Alumni". Columbia Public Schools Foundation. Archived from the original on 6 February 2012. Retrieved 2011-08-25.
- ↑ "A brief history of FairCom Corporation". FairCom Corporation. Retrieved 2011-08-25.
- ↑ "FairCom releases c-treeSQL Server and new edition of c-tree Plus incorporating an array of interface technology". FairCom Corporation. Retrieved 2011-08-25.
- ↑ "FairCom announces c-treeACE Express database engine". FairCom Corporation. Retrieved 2011-08-25.
- ↑ "FairCom Corperation". Retrieved 2017-11-03.
- ↑ "FairCom just announced a new edge computing database". Business Insider. Retrieved 2018-10-25.
External links[edit]
This article "C-treeACE" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:C-treeACE. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
