2014 | OriginalPaper | Chapter
Cloud Application Management Patterns
Authors : Christoph Fehling, Frank Leymann, Ralph Retter, Walter Schupeck, Peter Arbitter
Published in: Cloud Computing Patterns
Publisher: Springer Vienna
Activate our intelligent search to find suitable subject content or patents.
Select sections of text to find matching patents with Artificial Intelligence. powered by
Select sections of text to find additional relevant content using AI-assisted search. powered by
This chapter covers architectural patterns that describe how cloud applications as described in Chap.
4
, can be managed automatically by separate components (Fig. 5.1). These management components (Sect. 5.2) handle the automated management of cloud-native applications regarding dynamic elasticity, resiliency, updates etc. Due to the
pay-per-use
property of cloud applications covered in Sect.
1.1
, scaling tasks should be automated, because the number of provisioned IT resources, i.e., the number of provisioned virtual servers, the size of booked storage or the number of application component instances directly affects the runtime costs of an application. Furthermore,
environment-based availability
(88) assurances, where individual cloud resources can fail at any time, or a
node-based availability
(85) that does not meet requirements of an application, as well as network partitions, may create the need to monitor applications and automatically react to resource failures.