High-availability application architecture: Difference between revisions

Revision as of 00:16, 18 August 2009

Latest revision as of 23:40, 12 February 2025

(26 intermediate revisions by 17 users not shown)

Line 1:

{{refimprove|date=April 2009}}

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

In [[information technology]], '''high-availability application architecture''' is a process followed when implementing a new [[application software|application]] into an existing business-wide [[computer system]] or [[Enterprise resource planning|ERP]] while minimizing [[downtime]]. ff

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

The architecture contains three stages: [[Research and development|development]], [[quality assurance]], and [[Production (economics)|production]].

==Definition==

ThisIn definitionthe mustabove bedefinition, broke into two parts in order to be fully understood. "''[[Highhigh availability]]'' is "a [[design]] and [[implementation]] that ensures a certain degree of operational continuity.",<ref>{{Cite web | url=http://www.slideshare.net/davemitz/7-stages-of-scaling-web-applications |title = 7 Stages of Scaling Web Applications|date = 2008-08-06}}</ref> Applicationand ''[[application architecture is the second part, which]]'' refers to the actual concept and design of implementing a new [[configuration]] into the particular system.

==Summary==

In the IT world minimizing downtime is very important, and in order to implement a new configuration into an existing computer system one must follow strict architectural guidelines before releasing the new configuration into [[Production, costs, and pricing|production]]. Following the application architecture guidelines will greatly reduce the potential downtime when implementing a new configuration into an existing system.

==Stages of Architecturearchitecture==

As afore mentioned, thereThere are three stages that an application mostmust go through before it "goes live." All threeEach of these stages must pass through the ''transport directory'' before going on to the next stage.

===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 Assuranceassurance===

During the [[quality assurance]] stage the configuration settings, and program changes that impact the application are tested. If any [[fault (technology)|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 Directorydirectory==

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==

==References==

<references/>