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
architecture [2010/02/24 17:05]
biogridadmin
architecture [2010/04/23 14:30]
biogridadmin
Line 2: Line 2:
 The BioGRID database architecture consists of three distinct components: (i) the **[[core|Core]]** (ii) the **[[web|Web]]** (iii) the **[[Interaction_Management_System|Interaction Management System (IMS)]]**. This BioGRID data model was developed to be both extensible and modular. Each of the three components has a specific role in driving the BioGRID system and can easily be modified to meet rapidly changing needs in data management without entailing major changes to the applications it supports. In large databases, the integrity of the data model is often compromised (for example, by duplicating data within the database to speed up queries) to improve performance. This compromise frequently leads to serious problems with data integrity. Alternatively,​ a completely normalized database that strictly follows theoretical design principles, while maintaining data integrity, can often suffer greatly in performance,​ especially in cases where the database grows to a substantial size. The BioGRID data model solves this problem by utilizing a suite of tables specifically engineered to reduce query time while maintaining a structured normalized form that does not compromise fundamental design principles. The BioGRID database architecture consists of three distinct components: (i) the **[[core|Core]]** (ii) the **[[web|Web]]** (iii) the **[[Interaction_Management_System|Interaction Management System (IMS)]]**. This BioGRID data model was developed to be both extensible and modular. Each of the three components has a specific role in driving the BioGRID system and can easily be modified to meet rapidly changing needs in data management without entailing major changes to the applications it supports. In large databases, the integrity of the data model is often compromised (for example, by duplicating data within the database to speed up queries) to improve performance. This compromise frequently leads to serious problems with data integrity. Alternatively,​ a completely normalized database that strictly follows theoretical design principles, while maintaining data integrity, can often suffer greatly in performance,​ especially in cases where the database grows to a substantial size. The BioGRID data model solves this problem by utilizing a suite of tables specifically engineered to reduce query time while maintaining a structured normalized form that does not compromise fundamental design principles.
  
-All of the BioGRID databases use **[[http://​www.mysql.com/​|MySQL 5.1]]**. We chose MySQL as the database because it is freely available, platform independant,​ and easy to install and maintain without sacrificing performance or features. The BioGRID is thus fully portable to any academic environment+All of the BioGRID databases use **[[http://​www.mysql.com/​|MySQL 5.1]]**. We chose MySQL as the database because it is freely available, platform independant,​ and easy to install and maintain without sacrificing performance or features.
  
-{{ :​biogrid-data-model.jpg| }}+{{ :​biogrid-data-model.jpg |}}
  
 
architecture.txt · Last modified: 2017/08/08 12:52 (external edit)