High-availability application architecture: Difference between revisions

Revision as of 02:13, 13 April 2009

Revision as of 02:30, 13 April 2009

Line 1:

{{article issues|deadend=April 2009|intromissing=April 2009|unreferenced=April 2009}}

{{internallinks|date=April 2009}}

='''High Availability Application Architecture'''=

==Definition==

This definition must be broke into two parts in order to be fully understood. "[[High availability]] generallyis refersa to[[design]] theand amount of time[[implementation]] that ensures a particularcertain systemdegree isof availableoperarional for usecontinuity."<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==