GF.Data Engine: Difference between revisions
m (bullets) |
(slight text update + maturity) |
||
Line 1: | Line 1: | ||
{{Maturity| | {{Maturity|4}} | ||
{{Pageheaderbox4GF | {{Pageheaderbox4GF | ||
|name=Data Engine | |name=Data Engine | ||
|WorkingArea=Middleware | |WorkingArea=Middleware | ||
|version=0. | |version=0.2 | ||
|owner=J.A.H. Schoonderbeek | |owner=J.A.H. Schoonderbeek | ||
|summary=This function offers the ability to process strictly structured data. | |summary=This function offers the ability to process strictly structured data. | ||
}} | }} | ||
This function offers the ability to process strictly structured data, i.e. it controls the | This function offers the ability to process "strictly structured data", i.e. it controls the creation, updating and querying of sets of organized data. An example of a Data Engine is a database system. The function may offer one or more of the following: | ||
* a "modeling language" | * a "modeling language" | ||
* a "query language" | * a "query language" | ||
* a "transaction mechanism" | * a "transaction mechanism" | ||
Note that the Data Engine itself does not cater for the storage of strictly structured data (other than intermediate storage); to that end, the function should be combined with the Structured Data Store function. | Note that the Data Engine itself does not cater for the storage of strictly structured data (other than intermediate storage); to that end, the function should be combined with the Structured Data Store function. | ||
There are many types of databases that can be modelled using the Data Engine function, such as | |||
* Relational database; | |||
* Object-oriented database; | |||
* Document-oriented database; | |||
* Graph database; | |||
* Unstructured database. | |||
{{FunctionIcon | {{FunctionIcon | ||
|image=Icon GF Data Engine.png | |image=Icon GF Data Engine.png | ||
}} | }} | ||
{{Text Footer GF}} | {{Text Footer GF}} |
Latest revision as of 07:01, 7 October 2013
Page maturity This page has maturity level 4 (mature) |
GF | Data Engine | Version: | 0.2 | ||
---|---|---|---|---|---|
Document type: | Generic Function | Owner: |
This function offers the ability to process strictly structured data. |
Description
This Generic Function belongs to Working Area Middleware. This function offers the ability to process "strictly structured data", i.e. it controls the creation, updating and querying of sets of organized data. An example of a Data Engine is a database system. The function may offer one or more of the following:
- a "modeling language"
- a "query language"
- a "transaction mechanism"
Note that the Data Engine itself does not cater for the storage of strictly structured data (other than intermediate storage); to that end, the function should be combined with the Structured Data Store function.
There are many types of databases that can be modelled using the Data Engine function, such as
- Relational database;
- Object-oriented database;
- Document-oriented database;
- Graph database;
- Unstructured database.
Icon
The image "Icon GF Data Engine.png" (shown below) can be used to represent this infrastructure function in graphical Pattern representations that it might be part of:
Generic Patterns using this Generic Function
The following Generic Patterns use this function:
Applied Pattern | Owner | Maturity |
---|---|---|
Content Hosting | J.A.H. Schoonderbeek | 3 |
Data Management | S.A.D. Jumelet | 0 |
Applied versions of this Generic Function
The following variants of this function have been defined:
No Applied Pattern based on this Generic Pattern (yet)