High-availability application architecture: Difference between revisions

Content deleted Content added
Erik9bot (talk | contribs)
Line 3:
 
<!--Overview-->
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, 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==
Line 9:
 
==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 Architecture==
Line 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==