High-availability application architecture: Difference between revisions

Content deleted Content added
m alter pipe
 
(7 intermediate revisions by 6 users not shown)
Line 1:
{{Multiple issues|
{{refimprove|date=April 2009}}
{{orphan|date=July 2010}}
}}
 
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
 
The architecture contains three stages: [[Research and development|development]], [[quality assurance]], and [[Production, costs, and pricing(economics)|production]].
 
==Definition==
In the above definition, ''[[high 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> and ''[[application architecture]]'' refers to the actual concept and design of implementing a new configuration into the particular system.
 
==Summary==
Line 18 ⟶ 15:
 
===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===
Line 24 ⟶ 21:
 
===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==