Skip to content

Commit

Permalink
add requirements example for elasticity
Browse files Browse the repository at this point in the history
  • Loading branch information
gernotstarke committed Apr 25, 2024
1 parent 68e33f7 commit 94d2247
Show file tree
Hide file tree
Showing 3 changed files with 30 additions and 3 deletions.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ You have an environment that allows to run

### Build and test

In the root directory, run `docker-compose up`.
In the root directory, run `docker compose up`.



Expand Down
4 changes: 2 additions & 2 deletions requirements/F/_posts/2000-01-19-fast-startup-time.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: "Fast startup time"
title: "Fast startup time (less than 90 seconds)"
tags: efficient
related: time behaviour, speed, performance, startup-time
related: time behaviour, speed, performance, startup-time, elasticity
permalink: /requirements/fast-startup-time
---

Expand Down
27 changes: 27 additions & 0 deletions requirements/S/_posts/2023-09-03-scale-up-in-2-minutes.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
title: "Scale up in 2 Minutes"
tags: efficient, reliable
related: elasticity, scalability, performance
permalink: /requirements/scale-up-in-2-minutes
---

<div class="quality-requirement" markdown="1">


**Background**: A cloud-based web application, with a sudden increase in user traffic, such as during a promotional event or a major product launch. Auto-scaling features are available and configured.


**Response**: The system automatically detects the increase in load and provisions additional resources to handle the increased traffic, without human intervention.

**Metric**:
* Time to Scale: The system should begin scaling up additional resources within 2 minutes of detecting a 50% increase in traffic load.
* Resource Utilization: After scaling, CPU and memory utilization should stabilize at approximately 70%, ensuring that resources are neither underutilized (wasteful) nor overburdened (which could degrade performance).
* Performance Maintenance: The response time of the web application should not exceed 3 seconds for 95% of the requests, even during peak traffic.
Cost Efficiency: The cost of scaled resources should not exceed a 150% increase despite a 200% increase in traffic, emphasizing cost-effective scaling.

</div><br>

This requirement was created with help from [ChatGPT](https://chat.openai.com) by using the prompt `create a quality attribute scenario to describe a elasticity requirement for a web application`.



0 comments on commit 94d2247

Please sign in to comment.