What makes the FairCom DB multimodel approach unique is the way our NoSQL and SQL engines complement each other, working together or separately as necessary for your development. This page walks through some of the sleek ways our NoSQL and SQL models work together.
|
|
The Volume, Velocity, and Variety (commonly referred to as the “3Vs”) of data being captured today are at an all-time high, and projections are these attributes will only continue to grow exponentially. As the capacity for our computer systems to be able to digest, analyze, and make intelligent decisions from this explosion of data continues to improve, it is clear that you will need a database that is able to keep pace. Regardless where the data is coming from—system logs, machine sensors, financial data, health care information, or somewhere you have only dreamed of—rest assured FairCom DB will be able to keep pace with your dynamic data needs.
While the 3Vs of data are increasing, another dynamic is that data is no longer kept in proprietary silos. Virtually all industry segments need real-time methods for leveraging this valuable data for integration with other parts of the enterprise, business intelligence (BI), governance, web and mobile access, and so on.
With many database systems, an ETL (extract, transform, load) process is required to gain relational access to traditionally non-relational data. ETL creates two problems: (1) you now have two copies of data to maintain and; (2) you now have relational access over “stale” data, the D+1 problem. Additionally, some solutions are limited to read-only access to the exported SQL data.
SQL is the natural choice for external integration. With FairCom DB, applications remain as-is and schema requirements can “follow the data” allowing NoSQL data to come to life in SQL. With multi-schema and subrecord data, FILESET support, and on-the-fly types conversion via our types SDK, FairCom DB allows extensive access to nearly all forms of existing application data, whether schema, semi-schema, or schema-less.
|
To put these concepts into context, let’s look at a real-world application that involves time series data. On the left side of this diagram, you’ll see large Volumes of high-velocity data that is Variable in nature. In this particular example, we have financial data that has information packed into variable-size arrays to improve the speed and performance of writing data to disk as rapidly as possible. Rather than writing a single small record for each piece of financial data, the data is packed into large blocks, without a strict data schema, and pushed to disk as these blocks. Millions of data points per second are logged to disk with this technique. This is a good example of dynamic 3Vs data. Now, what happens when you want to perform data analysis over this dynamic data? Often the data will go through some form of ETL process on its way to a data warehouse or a relational database. But, if you leave the data in place and perform data analysis over the live data for reporting and web/enterprise/mobile device integration, you save a lot of time and you produce a wealth of opportunities for your business. You’ve also greatly lowered the strain on IT resources. You no longer need to move the data; you reduce system complexity by having a single source of data.
Only a true multimodel database supporting multiple data access techniques can address this very real modern example. This is a classic NoSQL case of schema-less data as it combines a variety of record types in a single table. This mix of formats is at odds with the relational model, which requires all records in a table to conform to a single schema (think of the third V, Variety). FairCom engineers overcame this problem with our unique Multi-Schema Data solution, which provides robust SQL access to non-relational data. When multi-schema data is accessed via SQL, we make it appear as multiple “virtual” tables, one for each schema. The SQL application is unaware of the non-relational structure of the underlying data, as it simply sees multiple “virtual” tables. Since the NoSQL portion of the application isn’t forced to impose a fixed schema over each piece of data being written to the database, the Volume and Velocity of data flowing through the application isn’t impacted. In this example, we show the benefits of FairCom DB for data flexibility, reduced code overhead, stellar data throughput, and ease of data integration and reporting through SQL. |
Get the WhitepaperLearn how to Achieve NoSQL Performance with Full Read/Write Access to SQL Features |
This C language API provides the maximum level of control and performance over the underlying data, and produces a very small footprint application. At this level, the relationship between data files and indexes is maintained for the programmer, while the programmer is responsible for record buffer management and individual relationships between files.
This C language API sits on top of the FairCom DB API and at this level the database takes care of record buffer management and concepts of sessions, databases and tables are introduced, further simplifying application coding.
This is a C++ implementation of the c‑treeDB C API.
This layer offers two APIs that are both identical to the c‑treeDB C API, except coded for easy use within C# and Visual Basic.
This layer is identical to the c‑treeDB C API, except coded for easy use within Embarcadero’s RAD Studio VCL framework.
This layer is a Java NoSQL implementation based on the object-oriented c-treeDB C++ API. This unique non-relational implementation provides a sizable performance gain (over 40%) over applications written using JDBC.
The c‑treeDB Java Enterprise Edition (JEE) offers an implementation of a Resource Adapter for JEE Application Servers such as Glassfish. It publishes FairCom DB NoSQL methods, which allows enterprise-class, distributed applications to view c‑treeACE data as a registered resource.
The c‑treeDB Java Persistence API (JPA) provides an object-oriented abstraction layer to manage relational data without the need to use SQL commands, which allows applications to be independent of any specific database. Unlike many SQL-based JPA implementations, such as Hibernate, FairCom makes available an alternative low-overhead, non-relational NoSQL based interface technology for improved performance for selected applications.
This product is a drop-in file system replacement for several of the more popular COBOL compilers: Microfocus, AccuCOBOL, Veryant’s IS COBOL, and RM/COBOL. This client-side driver leverages the Low-Level File System, NoSQL Key-Value Store, and c‑treeDB APIs to provide a means for existing COBOL applications to be modernized by providing a full database engine with full SQL access, replication, ACID transaction support, etc., all without making any code changes.
This product is written as a drop-in replacement for the Btrieve database. Like its sister, c‑treeRTG COBOL, this driver uses a blend of the Low Level and C Key-Value Store APIs and provides a quick way to migrate applications off the Btrieve database.
This is a server-side Open DataBase Connectivity (ODBC) driver that provides a subset of the SQL standard. This driver is primarily used for integration with other third-party applications such as report writers and BI tools. A direct link library is available for this API for use on Linux and Unix platforms.
This is a server-side, Type IV Java DataBase Connectivity (JDBC) driver, perfect for web integration and connecting to mobile devices. FairCom DB SQL JDBC provides an API that allows you to exploit Java’s “Write Once, Run Anywhere” capabilities for applications that run on different platforms and access enterprise data.
This is a drop-in native PHP module for interfacing this popular web interface into FairCom DB data.
This is a relational version of the c‑treeDB .NET NoSQL API. The advantage of using the relational ADO.NET version is it’s a more open standard and you’ll more easily find developer’s already familiar with this API.
This is a drop-in native Python module that interfaces with FairCom DB data through the well-known Python ctypes module. This architecture has been chosen because it makes the module immediately available for multiple Python implementations, such as PyPy and Jython.
This is an inline SQL API designed for developers who wish to embed SQL statements directly into their C/C++ programs.
This is a driver that provides access to FairCom DB data through applications created with Embarcadero’s Delphi or C++ Builder RAD development tools. Although ODBC or ADO.NET Drivers could be used for this integration, having a native dbExpress Driver simplifies the integration within this development framework. This relational DBX implementation is a sister to the FairCom DB VCL NoSQL API. The advantage of using the relational DBX version is it’s a more open standard and you’ll more easily find developers already familiar with this API.
TRY IT FOR YOURSELFExplore How FairCom DB Can Achieve Your Goals |
