InfinityDB is an embedded database engine first released in 8086 Assembly Language in 1988 and then in JAVA in 2002. InfinityDB can be deployed on servers, workstations, in hand-held devices and in distributed settings where there are multiple instances of the database engine performing data collection and consolidation. Programmers can design their own most efficient data model, or they can use the Entity-Attribute-Value item space method The patented Inversion function enables applications to compute and display indexes for any object, without having to maintain those indexes in the datastore. Absense of logging

Multiplicity of attributes and navigation paths typify an InfinityDB application, but the datastore is optimized for embedded systems. No pre-allocation of space is needed for multi-valued attributes, prefix and suffix compression is automatic, and uncommitted changes are not logged.

A global commit function replaces the need for logs and rollbacks,

and the addition of  therefore avoids the problems that more traditional DBMS systems face, such a avoids the use of logs, the need for administrative intervention, and the need to use any permanent storage beyond that required for its compressed data. Global commits initiated by application program calls at any desired frequency remove the need for logs in Version 1. Version 2 offers full ACID transactionality without the use of logs, by offering automatic programmatic control over roll backs.  

InfinityDB (earlier named Infinity Database Engine)has been deployed for use by end users in a wide range of fields, including video editing systems for sports, catagloging, programing tools, and collection and consolidation systems.

. An original use of InfinityDB and its Entity-Attribute-Value data model was in one of the earliest video editing systems, developed for Sports Tech International (later Lexicon) and marketed to professional and collegiate football, basketball, and baseball teams. Uses of the JAVA version vary from data collectionto programming tools. Embedded Databases present obstacles to successful deployment in end-user configurations, because they o use of logs to record all actions and roll backs to roll back the state of the database engine to a point where it has integrity, present problems in the embedded architecture domain where it is desirable to minimize the. ^[1]Among those problems are the need to append to flat files, which can become impractical with FLASH memory and the need for administrators to restore from logs so that the database can resume with fully sensible data. InfinityDB takes a different approach to these challenges with Version 1.0 of performing global updates at programmer-specified frequency, so that database is maintained in a viable state at all times, and with Version 2.0, employs programmatic control of roll backs, so that applications can control roll back functions automatically.