This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
integration:rawdata:home [2011/03/15 20:51] els |
integration:rawdata:home [2012/10/26 14:51] (current) |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| Omnidex is frequently used to allow high-performance searches against raw data files. Sometimes, the raw data files come from an [[admin:features:snapshots:home|Omnidex Snapshot]], which is an extracted copy of data from an underlying relational database. Other times, the raw data files are received from vendors such as credit services and list providers. Other times, the data is the output of an internal application, such as a log file or transaction file. Regardless of the source of the data, Omnidex will allow raw data files to be treated as a table within a database. | Omnidex is frequently used to allow high-performance searches against raw data files. Sometimes, the raw data files come from an [[admin:features:snapshots:home|Omnidex Snapshot]], which is an extracted copy of data from an underlying relational database. Other times, the raw data files are received from vendors such as credit services and list providers. Other times, the data is the output of an internal application, such as a log file or transaction file. Regardless of the source of the data, Omnidex will allow raw data files to be treated as a table within a database. | ||
| - | === Integrating at the Database Layer === | ||
| - | Integrating Omnidex into an application environment usually requires integration in two areas: the application (or client) layer, and the database (or server) layer. At the application layer, languages and tools generally use ODBC or JDBC to access the Omnidex SQL Engine. At the database layer, Omnidex is configured to access the underlying database. The Omnidex SQL Engine sits in between these layers, optimizing queries using the Omnidex indexes whenever possible. | ||
| - | {{:integration:integration_layers.png|}} | + | === Omnidex: A NoSQL Database === |
| - | + | ||
| - | === Omnidex: The NoSQL Database === | + | |
| Omnidex and raw data files are a well-tested and mature implementation of a NoSQL database. The NoSQL movement is a loose term describing databases that search data outside of the traditional relational database. NoSQL databases are designed to improve performance by not adhering to the ACID requirements for databases governing **A**tomicity, **C**onsistency, **I**solation and **D**urability. Raw data files are a classic implementation of this principle. Omnidex can index raw data files of enormous size and allow high-performance searches without the limitations of a relational database. | Omnidex and raw data files are a well-tested and mature implementation of a NoSQL database. The NoSQL movement is a loose term describing databases that search data outside of the traditional relational database. NoSQL databases are designed to improve performance by not adhering to the ACID requirements for databases governing **A**tomicity, **C**onsistency, **I**solation and **D**urability. Raw data files are a classic implementation of this principle. Omnidex can index raw data files of enormous size and allow high-performance searches without the limitations of a relational database. | ||