High-availability application architecture: Difference between revisions

Revision as of 11:26, 7 January 2015

Revision as of 01:07, 12 January 2016

Line 6:

}}

'''High availability application architecture''' is the process that is followed when implementing a new configuration into an existing [[Enterprise resource planning|ERP]]{{Clarify|date=July 2009}} system. The architecture contains three stages: 1)[[research and development|Development]], 2)[[Quality Assurance]], and 3)[[Production, costs, and pricing|Production]]. All three of these stages must pass through the transport directory before the following stage can be executed. This entire process is used to eliminate downtime when implementing an [[application software|application]].

<!--Overview-->

# [[research and development|Development]]

'''High availability application architecture''' is the process that is followed when implementing a new configuration into an existing [[Enterprise resource planning|ERP]]{{Clarify|date=July 2009}} system. The architecture contains three stages: 1)[[research and development|Development]], 2)[[Quality Assurance]], and 3)[[Production, costs, and pricing|Production]]. All three of these stages must pass through the transport directory before the following stage can be executed. This entire process is used to eliminate downtime when implementing an [[application software|application]].

# [[Quality Assurance]]

# [[Production, costs, and pricing|Production]].

All three of these stages must pass through the transport directory before the following stage can be executed. This entire process is used to eliminate downtime when implementing an [[application software|application]].

==Definition==

Line 29 ⟶ 32:

==Transport Directory==

The transport directory serves as a [[compiler]] for all of the changes to the application that occur through the stages. This component is the mechanism that allows the changes to be tracked from stage to stage. When the application is released for production, it will be delivered out of the transport directory.

==Process Diagram==

{{Empty section|date=July 2010}}

==References==

<references/>

2. MARATHON everRun http://en.wikipedia.org/wiki/Marathon_Technologies

[[Category:Information technology management]]