High-availability application architecture: Difference between revisions

Revision as of 01:27, 25 July 2009

Revision as of 00:16, 18 August 2009

Line 1:

{{Article issues|deadend=April 2009|intromissing=April 2009|unreferenced=April 2009|context =July 2009}}

{{Dead end|date=April 2009}}

<!--Overview-->

'''High availability application architecture''' is the process that is followed when implementing a new configuration into an existing [[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]].

==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 15 ⟶ 14:

===Development===

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

===Quality Assurance===

During the [[quality assurance]] stage the configuration settings, and program changes that impact the application are tested. If any [[faults]] are detected, they are corrected during this stage.

===Production===

The final stage that the application enters is the [[Production, costs, and pricing|production]] stage, which entails the actual system that a company runs its business on.

==Transport Directory==