High-availability application architecture
![]() | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
No issues specified. Please specify issues, or remove this template. |
![]() | This article needs more links to other articles to help integrate it into the encyclopedia. (April 2009) |
High availability application architecture is the process that is followed when implementing a new configuration into an existing ERP system. The architecture contains three stages: 1)Development, 2)Quality Assurance, and 3)Production. All three of these stages must pass through the transport directory before the following stage can be executed.
[Table of Contents]
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 operarional continuity."[1] 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. Following the application architecture guidelines will greatly reduce the potential downtime when implementing a new configuration into an existing system.