D. Meiländer, S. Gorlatch, C. Cappiello,V. Mazza, R. Kazhamiakin, and A. Bucchiarone: Using a Lifecycle Model for Adaptable Interactive Distributed Applications
D. Meiländer, S. Gorlatch, C. Cappiello,V. Mazza, R. Kazhamiakin, and A. Bucchiarone: Using a Lifecycle Model for Adaptable Interactive Distributed Applications
Similar to D. Meiländer, S. Gorlatch, C. Cappiello,V. Mazza, R. Kazhamiakin, and A. Bucchiarone: Using a Lifecycle Model for Adaptable Interactive Distributed Applications
Profit Maximization for Service Providers using Hybrid Pricing in Cloud Compu...Editor IJCATR
Similar to D. Meiländer, S. Gorlatch, C. Cappiello,V. Mazza, R. Kazhamiakin, and A. Bucchiarone: Using a Lifecycle Model for Adaptable Interactive Distributed Applications (20)
D. Meiländer, S. Gorlatch, C. Cappiello,V. Mazza, R. Kazhamiakin, and A. Bucchiarone: Using a Lifecycle Model for Adaptable Interactive Distributed Applications
1. Using a Lifecycle Model for Adaptable Interactive Distributed Applications D. Meiländer , S. Gorlatch, C. Cappiello, V. Mazza, R. Kazhamiakin, and A. Bucchiarone University of Muenster, Germany Politecnico di Milano, Italy Fondazione Bruno Kessler, Trentino, Italy ServiceWave 2010 13-15 December 2010
2.
3.
4.
5.
6.
7.
8.
9.
10. Mapping: Adaptation Triggers Adaptation Strategy 10 / 14 Adaptation trigger Monitored variable Adaptation trigger rule Adaptation strategy Change in QoS Update rate, throughput, resource usage, latency update rate < 25 updates/s user migration, replication or instancing Change in comput. context CPU and memory load, incoming / outgoing bandwidth CPU load > 90% user migration, replication or instancing Change in business context # concurrent users, # requests per app # concurrent users > user capability of app servers user migration, replication or instancing Prediction values number of users/hour, number of requests per application predicted users > current users + (threshold) QoS negotiation, replication or instancing/zoning
11.
12.
13.
14.
15.
Editor's Notes
(c) Prof. Dr. Klaus Pohl
(c) Prof. Dr. Klaus Pohl
(c) Prof. Dr. Klaus Pohl
Figure: Without RTF the developer must implement application logic and he must also manually implement mechanisms for distribution management, network communication, monitoring and controlling. Using RTF he must only implement the application logic because RTF handles all the other tasks for him (c) Prof. Dr. Klaus Pohl