Write a Blog >>
ICSE 2023
Sun 14 - Sat 20 May 2023 Melbourne, Australia

Cloud Fitness Engineering Presentation Proposal (300 words) An Accenture survey conducted in 2020 found that just 37% of companies had fully achieved their expected business outcomes from cloud. While cloud technology brings immense business benefits, its very nature and characteristics also come with challenges and risks. Most of these challenges are due to the cloud being distributed, heterogeneous, and hence highly complex in its functions, structure, interfaces, and interdependencies.

This presentation covers the following: 1. Aligning Cloud system design and architecture decisions to business success goals to: a. Unlock the value of Cloud b. Minimize distributed failures c. Optimize cloud resources commensurate with the business value

  1. Cloud Application QoS: How these decisions are reflected in Application Quality of Service KPIs like transaction throughput, latency, user response, error rates, availability, scalability, elasticity, threat surface limit, compliance, etc.

  2. We present the challenges and constraints in the current paradigms of design and testing of distributed applications (e.g., Cloud) from the process and tools perspective

  3. Cloud Fitness Engineering: We propose a novel paradigm of design, architecture, and testing of distributed applications to be fit-for-outcomes. We call this Cloud Fitness Engineering. Cloud Fitness Engineering adopts a continuous, iterative, and empirical approach to cloud system design and architecture. A continuous feedback loop of experiment, evaluate, discover, and improve cycle will progressively optimize the design and architecture to be aligned to deliver business outcomes. • Define business success goals • Derive Application QoS targets • Identify key system design and architecture decisions • Perform failure & degradation mode analysis • Design of Fitness Experiments • Conduct Fitness Experiments and use Observability tools to capture Application QoS behavior • Set up a continuous learning loop between DEV and OPS teams using a common Observability model • Optimize architecture decisions • Iterate

Case Study The Industry Talk will also present a case study