All Tags AWS ai algorithm-design architecture browser cloud cloud-efficiency cloud-principles cost-reduction data-centric data-compression data-processing deployment design documentation edge-computing email-sharing energy-efficiency energy-footprint enterprise-optimization green-ai hardware libraries llm locality machine-learning maintainability management measured microservices migration mobile model-optimization model-training multi-objective network-traffic parameter-tuning performance queries rebuilding scaling services storage-optimization strategies tabs template testing workloads

Tactic: Deallocate resources that are not used

Tactic sort: Awesome Tactic

Type: Architectural Tactic

Category: resource-allocation

Tags: scaling

Title

Deallocate resources that are not used

Description

Resources that are not used should be deallocated to save costs. This deallocation could be static (at a fixed moment in time) or dynamic (based on the changing environment). Selected services might not be required outside office hours (e.g., test environments). Hence, the workload could be architected to automatically deallocate resources during the evening, night, and weekend to save costs. If the workload is not used during a specific moment in time, switching off (idle) resources saves energy.

Participant

Cloud consumer

Related software artifact

Software resources

Context

Public cloud

Software feature

< unknown >

Tactic intent

Reducing the waste of resources

Target quality attribute

Cost-efficiency

Other related quality attributes

Energy-efficiency

Measured impact