High-availability application architecture: Difference between revisions

Revision as of 13:56, 24 August 2009

Revision as of 19:47, 16 October 2009

Line 2:

<!--Overview-->

'''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]].

==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 operational 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 14:

===Development===

The [[research and development|development]] stage is where [[Computer program|program]] changes, and [[configuration]] settings are modified to meet the needs of the new or existing system.

===Quality Assurance===