High-availability application architecture: Difference between revisions

Revision as of 09:52, 24 June 2009

Revision as of 09:48, 13 July 2009

Line 1:

{{article issues|deadend=April 2009|intromissing=April 2009|unreferenced=April 2009}}

{{internallinks|date=April 2009}}

{{context}}

<!--Overview-->

'''High availability application architecture''' is the process that is followed when implementing a new configuration into an existing [[ERP]]{{what}} system. The architecture contains three stages: 1)[[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]].

==Definition==

This definition must be broke into two parts in order to be fully understood. "[[High availability]] is a [[design]] and [[implementation]] that ensures a certain degree of operarionaloperational continuity."<ref>http://www.slideshare.net/davemitz/7-stages-of-scaling-web-applications</ref> Application architecture is the second part, which refers to the actual concept and design of implementing a new [[configuration]] into the particular system.

==Summary==

Line 30 ⟶ 31:

==References==

<references/>

{{uncategorized|date=May 2009}}

[[Category:Information technology management]]