| arguments |
To store the collected raw data in databases per system brings an extra boost in performance and parallel working abilities. But more it brings extra advantages in the administration and security side. It extends the possibility to move the schemas on different servers, if the load is more than expected, or even if one server moves to another. Further it brings separation of concern in the database schemas, so the backups could be planned per tool type and its database. A downside is it asks more administration needs then the one schema solution.
|
| is about | |
| decision_issue |
? For the data collector there 2 existing ways to store the extracted data from the different data sources (tool types)
|
| depends on | |
| design decision |
Decentralized data schema.
The decision is to use a database schema for every tool type. This decision is based on the conclusion above. The database schema per tool type brings the needed extensibility also on the administration side. It also brings flexibility in moving the schemas or even to delete them when no data Gatherer for this type exists.
|
| knowledge is located in | |
| name |
Data schema for tool types
|
| has alternative | |
| status |
Decided
|
| Class |
|
| Name |
Data schema for tool types
|