GP.File Storage - Revision history

Jan Schoonderbeek: typo in service link

2013-10-07T05:32:40Z

typo in service link

← Older revision		Revision as of 05:32, 7 October 2013
Line 50:		Line 50:
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.Authentication+~~Autorization~~		\|service=GS.Authentication+Authorization
	\|choice=May		\|choice=May
	\|reason=A&A will be required for one or more of the following uses:		\|reason=A&A will be required for one or more of the following uses:

Jan Schoonderbeek: fixed ref to data protection mgmt

2013-10-07T05:30:23Z

fixed ref to data protection mgmt

← Older revision		Revision as of 05:30, 7 October 2013
Line 5:		Line 5:
	\|version=0.5		\|version=0.5
	\|owner=J.A.H. Schoonderbeek		\|owner=J.A.H. Schoonderbeek
	\|summary=This Pattern offers functionality to manipulate (store, retrieve and modify et cetera) data in loosely structured form.		\|summary=This Pattern offers functionality to manipulate (store, retrieve and modify et cetera) data in loosely structured form (e.g. files).
	}}		}}
	This function enables a service that offers its consumers the ability to manipulate (store, retrieve and modify et cetera) data in [[OIAm_data_view\|loosely structured]]. The function may distribute the data over multiple logical locations, but makes its consumers view it as located in a single logical location. The function may also offer the ability to perform storage related "intelligent" tasks, such as replication, migration, encryption, reporting, compression and data deduplication.		This function enables a service that offers its consumers the ability to manipulate (store, retrieve and modify et cetera) data in [[OIAm_data_view\|loosely structured]]. The function may distribute the data over multiple logical locations, but makes its consumers view it as located in a single logical location. The function may also offer the ability to perform storage related "intelligent" tasks, such as replication, migration, encryption, reporting, compression and data deduplication.
Line 55:		Line 55:
	* permission validation for read/write/modification/deletion actions on the loosely structured data being stored;		* permission validation for read/write/modification/deletion actions on the loosely structured data being stored;
	* access to the more sensitive parts of the Controlling function, that may influence aspects of this Pattern's behaviour ranging from facility management to self-service provisioning of storage space;		* access to the more sensitive parts of the Controlling function, that may influence aspects of this Pattern's behaviour ranging from facility management to self-service provisioning of storage space;

	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.~~Backup~~ Management		\|service=GS.Data Protection Management
	\|choice=May		\|choice=May
	\|reason=Combining this Pattern with a ~~Backup~~ Management service serves to create secondary copies of the data stored by the Pattern, with the aim of being able to perform a (partial or complete) restore of the data, in the original location or an alternative location.		\|reason=Combining this Pattern with a Data Protection Management service serves to create secondary copies of the data stored by the Pattern, with the aim of being able to perform a (partial or complete) restore of the data, in the original location or an alternative location.

	Note that the ~~Backup~~ Management service is usually under control of IT Operations, but may occasionally be offered to ~~clients~~ directly. Depending on the way it's modelled, this may impact the Controlling function inside the Pattern.		Note that the Data Protection Management service is usually under control of IT Operations, but may occasionally be offered to consumers directly. Depending on the way it's modelled, this may impact the Controlling function inside the Pattern.
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row

Jan Schoonderbeek: slight text updates + maturity

2013-10-05T10:06:48Z

slight text updates + maturity

← Older revision		Revision as of 10:06, 5 October 2013
Line 1:		Line 1:
	{{Maturity\|3}}		{{Maturity\|4}}
	{{Pageheaderbox4GP		{{Pageheaderbox4GP
	\|name=File Storage		\|name=File Storage
Line 5:		Line 5:
	\|version=0.5		\|version=0.5
	\|owner=J.A.H. Schoonderbeek		\|owner=J.A.H. Schoonderbeek
	\|summary=This Pattern offers functionality to store, retrieve and modify data in loosely structured form.		\|summary=This Pattern offers functionality to manipulate (store, retrieve and modify et cetera) data in loosely structured form.
	}}		}}
	This ~~Pattern~~ offers ~~functionality~~ to store, retrieve and modify data in [[OIAm_data_view\|loosely structured]] ~~form~~. The ~~Pattern has~~ the ~~following characteristics:~~		This function enables a service that offers its consumers the ability to manipulate (store, retrieve and modify et cetera) data in [[OIAm_data_view\|loosely structured]]. The function may distribute the data over multiple logical locations, but makes its consumers view it as located in a single logical location. The function may also offer the ability to perform storage related "intelligent" tasks, such as replication, migration, encryption, reporting, compression and data deduplication.
	* located ~~at one~~ logical location,
	* may offer the ability to perform storage related "intelligent" tasks, such as replication, migration, encryption, compression and data deduplication~~. This intelligence may be characterized as~~
	** "back-end facing" intelligence; functionality that the facility's business clients don't get (direct) access to, only the administrators and back-end systems;
	** "front-end facing" intelligence; functionality that the facility's business clients can directly access and make use of.

	Note that File Storage is always implemented on top of some form of Raw Storage. As a consequence, an Applied Pattern dealing with file storage is often based on both the File Storage Generic Pattern and the [[GP.Raw Storage\|Raw Storage]] Generic Pattern.		Note that File Storage is always implemented on top of some form of Raw Storage. As a consequence, an Applied Pattern dealing with file storage is often based on both the File Storage Generic Pattern and the [[GP.Raw Storage\|Raw Storage]] Generic Pattern.

	As examples: realizations of File Storage (and Raw Storage under it) can include:		As examples: realizations of File Storage (and Raw Storage under it) can include:
	* Content Management Systems (CMS) and alike solutions,		* simple Content Management Systems (CMS) and alike solutions,
	* (the front-end of) NAS appliances,		* (the front-end of) NAS appliances,
	* file share servers.		* file share servers.
	Note: it's possible that the solution is to make use of Business Rules (e.g. for data deduplication or automatic migration of data to nearline/offline storage). If this is ~~the case,~~ then this ~~pattern~~ must be combined with the corresponding functions.		Note: it's possible that the solution is to make use of Business Rules (e.g. for data deduplication or automatic migration of data to nearline/offline storage). If this is to be modelled then this Pattern must be combined with the corresponding functions.
	{{Pattern Realizes		{{Pattern Realizes
	\|service=GS.File Storage		\|service=GS.File Storage
Line 33:		Line 29:
	\|function=GF.File Engine		\|function=GF.File Engine
	\|choice=Must		\|choice=Must
	\|reason=This function handles the actual storing/retrieving of loosely structured data such as (but not restricted to) files or documents. It serves ~~clients~~ such as end-users or systems (among which application engines and database servers)~~. To that end, this function offers a storage structure that fits the data to be stored, such as a file system for files, and an interface over which data can be offered or retrieved.~~		\|reason=This function handles the actual storing/retrieving of loosely structured data such as (but not restricted to) files or documents. It serves the needs of the File Storage service's consumers such as end-users or systems (among which application engines and database servers).
			Note that it requires access to Raw Storage services to physically store the bits and bytes that make up the instances of loosely structured data.
	The File Engine provides "intelligence" to the file storage solution with respect to its handling of the stored data, with the aim of meeting the quality requirements, improving infrastructure management, and/or providing sufficient performance. It may handle migration/replication to other instances of itself, encryption, reduction, de-duplication and other "standard" storage-related processing. It also can handle granular, file-based permissions.
	Note that it requires access to Raw Storage services to physically store the bits and bytes that make up the instances of loosely structured data.
	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
	\|function=GF.Controlling		\|function=GF.Controlling
	\|choice=Must		\|choice=Must
	\|reason=This function can be used by authorized administrators (and ~~possibly authorized clients~~) to change the behaviour of the Pattern~~. Examples are:~~		\|reason=This function can be used by authorized consumers (such as administrators and users) to change the behaviour of the Pattern.
	* Restoring (partial) back-ups;
	* Capacity & Performance Management;
	* Provisioning;
	* Rules Management, with which the stored data can be manipulated using metadata, usage, usage patterns, or other information that the Pattern may hold or obtain.

	~~Care must be taken to limit access to this function to authorized systems and users~~.
	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
	\|function=GF.Caching		\|function=GF.Caching
	\|choice=May		\|choice=May
	\|reason=The Pattern may use caching functionality to increase its capacity to receive and/or return data on request.		\|reason=The Pattern may use caching functionality to increase its capacity to receive and/or return data on request.
	}}		}}
	{{Table Ending}}		{{Table Ending}}
Line 59:		Line 47:
	\|service=GS.Raw Storage		\|service=GS.Raw Storage
	\|choice=Must		\|choice=Must
	\|reason=All "loosely structured data" eventually will have to be stored on some physical device, where it is treated as "unstructured data~~" or "raw bits~~". ~~Putting~~ this Service under the File Storage pattern delivers this ability.		\|reason=All "loosely structured data" eventually will have to be stored on some physical device, where it is treated as "unstructured data". Placing this Service under the File Storage pattern delivers this ability.
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
Line 65:		Line 53:
	\|choice=May		\|choice=May
	\|reason=A&A will be required for one or more of the following uses:		\|reason=A&A will be required for one or more of the following uses:
	* access to the Controlling function, that may influence aspects of this Pattern's behaviour ranging from facility management to self-service provisioning of storage space;
	* permission validation for read/write/modification/deletion actions on the loosely structured data being stored;		* permission validation for read/write/modification/deletion actions on the loosely structured data being stored;
	* ~~permission validation for actions such as backup~~, ~~restore and archiving.~~		* access to the more sensitive parts of the Controlling function, that may influence aspects of this Pattern's behaviour ranging from facility management to self-service provisioning of storage space;

	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.Backup Management		\|service=GS.Backup Management
	\|choice=May		\|choice=May
	\|reason=Combining this Pattern with a Backup Management service ~~always~~ serves to create secondary copies of the data stored by the Pattern, with the aim of being able to perform a (partial or complete) restore of the data, in the original location or an alternative location.		\|reason=Combining this Pattern with a Backup Management service serves to create secondary copies of the data stored by the Pattern, with the aim of being able to perform a (partial or complete) restore of the data, in the original location or an alternative location.

	Note that the Backup Management service is usually under control of IT Operations, but may occasionally be offered to clients directly. ~~This impacts~~ the Controlling function inside the Pattern.		Note that the Backup Management service is usually under control of IT Operations, but may occasionally be offered to clients directly. Depending on the way it's modelled, this may impact the Controlling function inside the Pattern.
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.Archive Management		\|service=GS.Archive Management
	\|choice=May		\|choice=May
	\|reason=Combining this Pattern with an Archive Management service ~~always~~ serves to create a primary copy of the data stored by the Pattern at a different physical location. This can be to satisfy legal or other user requirements, or to free up storage space in this Pattern.		\|reason=Combining this Pattern with an Archive Management service serves to create a primary copy of the data stored by the Pattern at a different physical location. This can be to satisfy legal or other user requirements, or to free up storage space in this Pattern.

	Note that the Archive Management service is usually under control of IT Operations, but may occasionally be offered to clients directly. ~~This impacts~~ the Controlling function inside the Pattern.		Note that the Archive Management service is usually under control of IT Operations, but may occasionally be offered to clients directly. Depending on the way it's modelled, this may impact the Controlling function inside the Pattern.
	}}		}}
	{{Table Ending}}		{{Table Ending}}
	{{Text Footer GP}}		{{Text Footer GP}}

Jan Schoonderbeek: GP added

2013-05-07T13:54:14Z

GP added

New page

{{Maturity|3}}
{{Pageheaderbox4GP
|name=File Storage
|sector=Core
|version=0.5
|owner=J.A.H. Schoonderbeek
|summary=This Pattern offers functionality to store, retrieve and modify data in loosely structured form.
}}
This Pattern offers functionality to store, retrieve and modify data in [[OIAm_data_view|loosely structured]] form. The Pattern has the following characteristics:
* located at one logical location,
* may offer the ability to perform storage related "intelligent" tasks, such as replication, migration, encryption, compression and data deduplication. This intelligence may be characterized as
** "back-end facing" intelligence; functionality that the facility's business clients don't get (direct) access to, only the administrators and back-end systems;
** "front-end facing" intelligence; functionality that the facility's business clients can directly access and make use of.

Note that File Storage is always implemented on top of some form of Raw Storage. As a consequence, an Applied Pattern dealing with file storage is often based on both the File Storage Generic Pattern and the [[GP.Raw Storage|Raw Storage]] Generic Pattern.

As examples: realizations of File Storage (and Raw Storage under it) can include:
* Content Management Systems (CMS) and alike solutions,
* (the front-end of) NAS appliances,
* file share servers.
Note: it's possible that the solution is to make use of Business Rules (e.g. for data deduplication or automatic migration of data to nearline/offline storage). If this is the case, then this pattern must be combined with the corresponding functions.
{{Pattern Realizes
|service=GS.File Storage
}}
{{Pattern Graphic
|graphic=GP.File Storage.png
|size=500px
|title=Generic Pattern for File Storage
|kind=Generic
}}
{{Generic Pattern Composition}}
{{Generic Pattern Composition Row
|function=GF.File Engine
|choice=Must
|reason=This function handles the actual storing/retrieving of loosely structured data such as (but not restricted to) files or documents. It serves clients such as end-users or systems (among which application engines and database servers). To that end, this function offers a storage structure that fits the data to be stored, such as a file system for files, and an interface over which data can be offered or retrieved.

The File Engine provides "intelligence" to the file storage solution with respect to its handling of the stored data, with the aim of meeting the quality requirements, improving infrastructure management, and/or providing sufficient performance. It may handle migration/replication to other instances of itself, encryption, reduction, de-duplication and other "standard" storage-related processing. It also can handle granular, file-based permissions.
Note that it requires access to Raw Storage services to physically store the bits and bytes that make up the instances of loosely structured data.
}}
{{Generic Pattern Composition Row
|function=GF.Controlling
|choice=Must
|reason=This function can be used by authorized administrators (and possibly authorized clients) to change the behaviour of the Pattern. Examples are:
* Restoring (partial) back-ups;
* Capacity & Performance Management;
* Provisioning;
* Rules Management, with which the stored data can be manipulated using metadata, usage, usage patterns, or other information that the Pattern may hold or obtain.

Care must be taken to limit access to this function to authorized systems and users.
}}
{{Generic Pattern Composition Row
|function=GF.Caching
|choice=May
|reason=The Pattern may use caching functionality to increase its capacity to receive and/or return data on request.
}}
{{Table Ending}}
{{Pattern Adjacent Services}}
{{Generic Pattern Adjacent Service Row
|service=GS.Raw Storage
|choice=Must
|reason=All "loosely structured data" eventually will have to be stored on some physical device, where it is treated as "unstructured data" or "raw bits". Putting this Service under the File Storage pattern delivers this ability.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Authentication+Autorization
|choice=May
|reason=A&A will be required for one or more of the following uses:
* access to the Controlling function, that may influence aspects of this Pattern's behaviour ranging from facility management to self-service provisioning of storage space;
* permission validation for read/write/modification/deletion actions on the loosely structured data being stored;
* permission validation for actions such as backup, restore and archiving.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Backup Management
|choice=May
|reason=Combining this Pattern with a Backup Management service always serves to create secondary copies of the data stored by the Pattern, with the aim of being able to perform a (partial or complete) restore of the data, in the original location or an alternative location.

Note that the Backup Management service is usually under control of IT Operations, but may occasionally be offered to clients directly. This impacts the Controlling function inside the Pattern.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Archive Management
|choice=May
|reason=Combining this Pattern with an Archive Management service always serves to create a primary copy of the data stored by the Pattern at a different physical location. This can be to satisfy legal or other user requirements, or to free up storage space in this Pattern.

Note that the Archive Management service is usually under control of IT Operations, but may occasionally be offered to clients directly. This impacts the Controlling function inside the Pattern.
}}
{{Table Ending}}
{{Text Footer GP}}