PAT.Data Management

Informational

Page maturity
This page has maturity level 3 (usable)

	PAT	Data Management	Version:	0.22
	Document type:	Pattern Type	Owner:	J.A.H. Schoonderbeek

Informational

Create commentary

Description

This Pattern Type belongs to "Infrastructure Sector Core". This pattern provides a description of generic data management facilities. The most common realization of this functionality is known as 'database'.

Graphical Overview

This is the graphical representation of the infrastructure functions in this Pattern Type, plus their main relations:

(The source file of this picture can be downloaded here).

Pattern Type Composition

This pattern has the following mandatory and optional subfunctions, expressed in Building Block Types:

Icon	Function	WA	Inclusion	Rationale
	Structured Data Store	MW	mandatory	The structured storage of data is the heart of the Data Management pattern. Data is organized in such a way, that information can easily be retrieved, for example by a query, executed by a Data Engine facility.
	Data Engine	SE	mandatory	The Data Engine offers various ways to preserve, retrieve, manipulate and manage data that is being stored in a structured data store facility.
	Control Interface	SE	optional	A Data Management system should preferably be managed by a centralized facility. However, it may be desirable to manage the facility directly - and the Control Interface offers this means.
	Backup	ST	optional	This facility provides a means to back-up data for recovery purposes. Since the data stored may have all sorts of internal consistencies, and may undergo multiple operations at any time, the creation of a consistent point-in-time backup is a specialized job that can usually not be handled by generic backup facilities.
	Restore	ST	optional	The facility includes the means to restore a back-up as created by the Back-up functionality.
	Archiving	ST	optional	This facility preserves data in a persistent way. Archiving parts of a structured data storage requires knowledge of the internal structure of the data, and is thus specific to the implementation of the structured data store.

Pattern Type Neighbors

This pattern has the following mandatory and optional relations with adjacent (sub)functions, expressed in Pattern Types (PAT). Note: if the table below is empty, then there are no architecturally prescribed relations with adjacent subfunctions:

Function	Adjacency	Description
Application Hosting	optional	This Pattern is often a consumer of the services of Data Management.
Authentication & Authorization	optional	A suitable source for identity and permission information may be required for controlling access to the data stored in the Data Management facility; management of the data, or the Data Management facility itself, using the Control Interface.
File Storage	optional	The Structured Data Store usually needs to be stored itself on a facility, usually as loosely structured data (e.g. a set of files holding a database). To this end, File Storage can be used to model this storage.

Pattern Variants based on this type

No Patterns Variants implement this Type (yet)