PD.Relational Data Management: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Maturity | {{Maturity}} | ||
{{Pageheaderbox4PD | {{Pageheaderbox4PD | ||
|name=Relational Data Management | |name=Relational Data Management | ||
| Line 12: | Line 12: | ||
* a "transaction mechanism", to enable interaction with other (instances of) data management facilities and applications. | * a "transaction mechanism", to enable interaction with other (instances of) data management facilities and applications. | ||
These elements are provided by the [[DOT.Data|Data]] [[FD.Engine|Engine]]. Data objects are stored using a predefined (structured) [[DOT.Data|Data]] [[FD.Store|Store]]. Both functions form the core of this Pattern. | These elements are provided by the [[DOT.Data|Data]] [[FD.Engine|Engine]]. Data objects are stored using a predefined (structured) [[DOT.Data|Data]] [[FD.Store|Store]]. Both functions form the core of this Pattern. | ||
{{Pattern Realizes | {{Pattern Realizes | ||
|service=SD.Application Database | |service=SD.Application Database | ||
| Line 18: | Line 17: | ||
{{Pattern Definition Graphic | {{Pattern Definition Graphic | ||
|graphic=PD.Relational Data Management.png | |graphic=PD.Relational Data Management.png | ||
|size=800px | |size=800px | ||
|title=Relational Data Management pattern | |title=Relational Data Management pattern | ||
}} | |||
{{Pattern Definition Composition}} | {{Pattern Definition Composition | ||
|Row_dataobjectype=DOT.Traffic | |||
}} | |||
{{Pattern Definition Composition Row | {{Pattern Definition Composition Row | ||
|function=FD.Engine | |function=FD.Engine | ||
| | |datobjecttype=DOT.Data | ||
|choice=Must | |choice=Must | ||
|reason=The Data Engine is the heart of the pattern, as it offers the intelligence to control strictly structured data handling. | |reason=The Data Engine is the heart of the pattern, as it offers the intelligence to control strictly structured data handling. | ||
| Line 31: | Line 31: | ||
{{Pattern Definition Composition Row | {{Pattern Definition Composition Row | ||
|function=FD.Store | |function=FD.Store | ||
| | |datobjecttype=DOT.Table | ||
|choice=Must | |choice=Must | ||
|reason=The Table Store offers the predefined storage structure. This is one of the key characteristics of relational data management. | |reason=The Table Store offers the predefined storage structure. This is one of the key characteristics of relational data management. | ||
| Line 37: | Line 37: | ||
{{Pattern Definition Composition Row | {{Pattern Definition Composition Row | ||
|function=FD.Encryption | |function=FD.Encryption | ||
| | |datobjecttype=DOT.Traffic | ||
|choice=May | |choice=May | ||
|reason=When data is exchanged over unsecured data transport facilities, it might be a good measure to encrypt the data at engine level. | |reason=When data is exchanged over unsecured data transport facilities, it might be a good measure to encrypt the data at engine level. | ||
}} | }} | ||
{{Pattern Definition Composition Row | |||
|function=FD.Caching | |||
|datobjecttype=DOT.Transaction | |||
|choice=May | |||
|reason=This function retains frequent issued transactions/queries, in order to improve performance. | |||
}} | |||
{{Table Ending}} | |||
{{Table Ending}} | {{Table Ending}} | ||
Revision as of 16:09, 27 November 2019
 | Page maturity This page has maturity level 8 (undefined) |
|
PD | Relational Data Management | Version: | 0.3 | 
|
|---|---|---|---|---|---|
| Document type: | Pattern Definition | Owner: |
 | This Pattern provides the function layout to model "strictly structured data" handling, in a relational fashion. |
Description
This Pattern Definition serves the creation of models in the Service Category "Data Management". This Pattern provides the function layout to model "strictly structured data" handling, i.e. it controls the creation, updating and querying of sets of organized data. It is called 'relational data management', because a schema is used to store data in a predefined way, with predefined relations between data objects. The provisioning of the following elements is important with this kind of data handling:
- a "modeling language", to define schemas;
- a "query language", to enable data object reading, creating, updating, and deleting;
- a "transaction mechanism", to enable interaction with other (instances of) data management facilities and applications.
These elements are provided by the Data Engine. Data objects are stored using a predefined (structured) Data Store. Both functions form the core of this Pattern.
Services realized
This Pattern realizes the following service(s):
- Application Database (This service provides a data store for applications with a predefined structure)
Functional and Integration view
This is the graphic representation of the function model of this Pattern Definition:
Pattern Definition Composition
This pattern is an aggregation of the following (mandatory and optional) functions, expressed in Data/Object Types and Fundtion Definitions:
| Function | Inclusion | Description/Rationale |
| no link Engine | recommended | The Data Engine is the heart of the pattern, as it offers the intelligence to control strictly structured data handling. |
| no link Store | recommended | The Table Store offers the predefined storage structure. This is one of the key characteristics of relational data management. |
| no link Encryption | optional | When data is exchanged over unsecured data transport facilities, it might be a good measure to encrypt the data at engine level. |
| no link Caching | optional | This function retains frequent issued transactions/queries, in order to improve performance. |
|}