This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:admin:architecture:multiple [2011/01/10 16:28] els |
admin:admin:architecture:multiple [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| - | ====== Omnidex Administration ====== | + | ====== Administration: Administration Basics ====== |
| ===== Omnidex Architecture ===== | ===== Omnidex Architecture ===== | ||
| - | [[admin:admin:architecture|Overview]] -> [[admin:admin:architecture:single|Single Server]] -> **[[admin:admin:architecture:multiple|Multiple Servers]]** -> [[admin:admin:architectures:snapshots|Omnidex Snapshots]] -> [[admin:admin:architectures:grids|Omnidex Grids]] -> [[admin: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]] |
| + | ---- | ||
| - | ===== Multiple Servers Architecture ====== | + | ==== Multiple Servers Architecture ==== |
| More complex architectures usually involve more servers. Traditionally, the web server, the application server and the data servers are all separate machines. This allows scalability by allowing more web servers and application servers for a given data server. Similarly, Omnidex is usually assigned its own server. This insures that proper resources can be assigned to each component of the architecture. | More complex architectures usually involve more servers. Traditionally, the web server, the application server and the data servers are all separate machines. This allows scalability by allowing more web servers and application servers for a given data server. Similarly, Omnidex is usually assigned its own server. This insures that proper resources can be assigned to each component of the architecture. | ||
| Line 15: | Line 17: | ||
| This strategy can increase the time required for building the indexes; however, this is still usually the preferred solution. When Omnidex reads the relational tables while building the indexes, the data must travel across the network between the servers, slowing this process down. Since indexes are built periodically, yet accessed frequently, it is still favorable to insure Omnidex has the resources needed to process queries. | This strategy can increase the time required for building the indexes; however, this is still usually the preferred solution. When Omnidex reads the relational tables while building the indexes, the data must travel across the network between the servers, slowing this process down. Since indexes are built periodically, yet accessed frequently, it is still favorable to insure Omnidex has the resources needed to process queries. | ||
| - | As systems become more complex, many businesses use Omnidex Snapshots to provide further performance and flexibility, as shown in this [[admin:admin:architectures:snapshots|Omnidex Snapshots]] system. | + | As systems become more complex, many businesses use Omnidex Snapshots to provide further performance and flexibility, as discussed in the [[admin:admin:architecture:snapshots|Omnidex Snapshots]] section. |
| - | **[[admin:admin:architecture:single|Prev]]** | **[[admin:admin:architectures:snapshots|Next]]** | + | ==== ==== |
| + | **[[admin:admin:architecture:single|Prev]]** | **[[admin:admin:architecture:snapshots|Next]]** | ||
| + | ====== Additional Resources ====== | ||
| + | |||
| + | See also: | ||
| + | |||
| + | {{page>:admin:admin:see_also&nofooter&noeditbtn}} | ||
| {{page>:bottom_add&nofooter&noeditbtn}} | {{page>:bottom_add&nofooter&noeditbtn}} | ||