Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
admin:admin:architecture:home [2011/01/10 18:49]
els
admin:admin:architecture:home [2016/06/28 22:38] (current)
Line 1: Line 1:
 +~~NOTOC~~
 +
 {{page>:​top_add&​nofooter&​noeditbtn}} {{page>:​top_add&​nofooter&​noeditbtn}}
  
Line 5: Line 7:
 ===== Omnidex Architecture ====== ===== Omnidex Architecture ======
  
-**[[admin:​admin:​architecture:​home|Overview]]** ​-> [[admin:​admin:​architecture:​single|Single Server]] ​-> [[admin:​admin:​architecture:​multiple|Multiple Servers]] ​-> [[admin:​admin:​architecture:​snapshots|Omnidex Snapshots]] ​-> [[admin:​admin:​architecture:​grids|Omnidex Grids]] ​-> [[admin:​admin:​architecture:​parallel|Parallel Servers]]+**[[admin:​admin:​architecture:​home|Overview]]** ​[[admin:​admin:​architecture:​single|Single Server]] ​[[admin:​admin:​architecture:​multiple|Multiple Servers]] ​[[admin:​admin:​architecture:​snapshots|Omnidex Snapshots]] ​[[admin:​admin:​architecture:​grids|Omnidex Grids]] ​[[admin:​admin:​architecture:​parallel|Parallel Servers]]
 ---- ----
  
 ==== Overview ==== ==== Overview ====
  
-Omnidex easily integrates into a wide variety of system architectures. ​ In many ways, Omnidex is like a database on a data server. ​ Omnidex provides flexibility and performance through a standard [[admin:admin:​sqlengine:​home|SQL engine]] that accesses a variety of data sources. Applications connect using standard [[dev:​odbc:​home|ODBC]] and [[dev:​jdbc:​home|JDBC]] interfaces, allowing Omnidex to plug into system architectures with little effort.+Omnidex easily integrates into a wide variety of system architectures. ​ In many ways, Omnidex is like a database on a data server. ​ Omnidex provides flexibility and performance through a standard [[admin:basics:​sqlengine:​home|SQL engine]] that accesses a variety of data sources. Applications connect using standard [[dev:​odbc:​home|ODBC]] and [[dev:​jdbc:​home|JDBC]] interfaces, allowing Omnidex to plug into system architectures with little effort. 
 + 
 +{{:​admin:​admin:​architecture:​basic_architecture.png|}}
  
 Many businesses have a substantial investment in a relational database. ​ For those businesses, Omnidex works alongside the relational database, preserving the corporate investment in the relational technology. ​ Applications can direct specific queries to Omnidex while leaving other operations in the hands of the relational database. ​ Architects choose the level of involvement of Omnidex in the application. Many businesses have a substantial investment in a relational database. ​ For those businesses, Omnidex works alongside the relational database, preserving the corporate investment in the relational technology. ​ Applications can direct specific queries to Omnidex while leaving other operations in the hands of the relational database. ​ Architects choose the level of involvement of Omnidex in the application.
Line 25: Line 29:
 **[[admin:​admin:​architecture:​single|Next]]** **[[admin:​admin:​architecture:​single|Next]]**
  
 +====== Additional Resources ======
 +
 +See also: 
 +{{page>:​admin:​admin:​see_also&​nofooter&​noeditbtn}}
 {{page>:​bottom_add&​nofooter&​noeditbtn}} {{page>:​bottom_add&​nofooter&​noeditbtn}}
 
Back to top
admin/admin/architecture/home.1294685398.txt.gz · Last modified: 2016/06/28 22:38 (external edit)