Menu
FusionLDB vs QLDB
The technology from Ld8a is far more functionally rich than the technology underpinning the QLDB offering. Ld8a technology goes way further by offering a fully functional relational development environment enabling complex business requirements to be readily addressed both for application development and for reporting needs.
Ld8a technology is wholly a database solution
First and foremost Ld8a technology is a database solution. All data using Ld8a technology is held in a database and therefore all data manipulation takes place in the database. i.e. all logical inserts, updates and deletes are captured within database table records and the table records are secured by cryptographically locking all records within the database. As all database insert, update and delete activities result in records being appended to the database, the database can be completely cryptographically secured.
The key feature of FusionLDB is the ability to convert logical INSERT, UPDATE and DELETE events (and corrections to these events) into physical INSERT journal entries. FusionLDB allows you to navigate to any journal entry point in the system of record and see the full state of the cryptographically locked relationally consistent database.
QLDB is a combination of a database and a document file system which is inefficient and additionally limits the scope of possible functionality.
Ld8a supports full relational capabilities
The relational model is widely recognised as the most preferable data management approach for complex business transactions. In this regard Ld8a technology provides comprehensive relational database capabilities.
Ld8a supports relational database tuning
As Ld8a technology makes unhindered use of the relational database infrastructure, all solutions can be tuned through the use of the relational database system facilities such as indexing, partitioning etc… This means that individual systems can be optimised for the performance requirements of each particular business and technical solution.
FusionLDB is "time friendly" and therefore "developer friendly"
All business systems require the ability to “correct” data entry. No business system is free
All business systems require the ability to “correct” and update data. No business system is free from mistakes needing to be corrected, or data requiring amendment when new facts come to light, or belated entry of data because it wasn’t to hand when a transaction was first created. The upshot of this is that the database needs to easily provide the reporting answers to the audit question “what did you know and when did you know it”. One huge advantage of Ld8a technology is the capability to capture all these events such that the system provides fully relational access to the “Current state” of data, the “History” of changes ie normal updates, as well as – and critically – “Corrections” to the data history. To exemplify the importance of this, business decisions such as insurance cover are determined by the known facts at a point in time or over a period of time. If these facts are updated or corrected, the point in time these updates are entered in the system and the period of effect of these updates is absolutely critical for audit and the basis of decisions. Ld8a technology enables the easy capture of these events in the context of time as well as great simplicity in the reporting against events. While QLDB captures updates in the audit log, the data is not in a readily accessible state for reporting ie there is a significant application and reporting development overhead to provide this capability – if in deed it is possible at all!
from mistakes needing to be corrected, or data requiring amendment when new facts come to light, or belated entry of data because it wasn’t to hand when a transaction was first created. The upshot of this is that the database needs to easily provide the reporting answers to the audit question “what did you know and when did you know it”. One huge advantage of Ld8a technology is the capability to capture all these events such that the system provides fully relational access to the “Current state” of data, the “History” of changes ie normal updates, as well as – and critically – “Corrections” to the data history. To exemplify the importance of this, business decisions such as insurance cover are determined by the known facts at a point in time or over a period of time. If these facts are updated or corrected, the point in time these updates are entered in the system and the period of effect of these updates is absolutely critical for audit and the basis of decisions. Ld8a technology enables the easy capture of these events in the context of time as well as great simplicity in the reporting against events. While QLDB captures updates in the audit log, the data is not in a readily accessible state for reporting ie there is a significant application and reporting development overhead to provide this capability – if in deed it is possible at all!
Ld8a is ACID compliant
Ld8a uses the power of the relational database infrastructure to provide ACID compliance. ACID (Atomicity, Consistency, Isolation, Durability) is a set of properties of database transactions intended to guarantee validity even in the event of errors, power failures, etc…
Ld8a uses the power of the relational database infrastructure to provide ACID compliance. ACID (Atomicity, Consistency, Isolation, Durability) is a set of properties of database transactions intended to guarantee validity even in the event of errors, power failures, etc… As Ld8a is wholly a database solution the events which can cause data inconsistency can be handled. In the case of QLDB there are two sources of the truth – the database and the journal file system – meaning that system errors or failures can cause data inconsistencies between the database and the journal. Once there is more than one source of the truth additional checks and maintenance need to be provided. As a simple example, if the QLDB database was updated, but system problems meant the journal entry wasn’t completed, what then happens?
Ld8a provides superior SQL access
Ld8a uses the relational database infrastructure enabling data to be fully manipulated through SQL and SQL-like commands. That is to say, developers manipulate and query data in Ld8a database systems using standard SQL commands. The SQL commands are performed on data that is held “relationally” in tables and the SQL is completely familiar to SQL trained developers. QLDB also provides an SQL-like language but can only be sub-optimal where the SQL is applied when querying the document based journal file repositories. Ld8a technology wholly uses the relational database environment for which SQL is designed.
Important FusionLDB Concepts
Ledger
A FusionLDB ledger consists of a set of relational database tables which contain all application records and journal entry records. The tables maintain a complete and immutable data history of all application data changes.
Table
Tables exist within FusionLDB with full relational capabilities. Tables have full access to the RDBMS environment such that the database can be tuned with normal relational database methods.
Time friendly
As the FusionLDB ledger methodology is append only, FusionLDB manages all aspects of time in respect to application data such that application development is hugely simplified.
Serverless
FusionLDB can be deployed in any cloud compute environment supported by the relational database environment (which is probably any cloud platform!).
Journal
A journal consists of a sequence of cryptographically chained records so that changes can be verified. The key feature of FusionLDB is the ability to convert logical INSERT, UPDATE and DELETE events (and corrections to these events) into physical INSERT journal entries. FusionLDB allows you to navigate to any journal entry point in the system of record and see the full state of the cryptographically locked relationally consistent database.
Current View Data Modelling
FusionLDB allows the developer to define and operate off a standard, current view relational data model. This simplifies the modelling process as there is no requirement to accommodate audit tables. The FusionLDB environment automatically provides full system of record audit trails.
SQL
FusionLDB uses standard SQL.
Time series and point in time reporting
As data is held in a very time friendly pattern, FusionLDB enables complex point in time and time series reporting to be undertaken with great simplicity. FusionLDB enables the production of time based reports which in many circumstances would typically require the development of additional data warehouse solutions.