All Tags
AWS
algorithm-design
architecture
cloud-principles
cost-reduction
data-centric
data-compression
data-processing
deployment
design
edge-computing
energy-footprint
hardware
libraries
locality
machine-learning
management
measured
migration
model-optimization
model-training
performance
queries
rebuilding
scaling
services
strategies
template
workloads
Tactic: Use batch instead of real-time data processing
Tactic sort:
Awesome Tactic
Type: Architectural Tactic
Category: resource-adaptation
Tags:
data-processing
Title
Use batch instead of real-time data processing
Description
If the system objectives allow, transporting data in batches rather than in real-time could optimize the costs as there is less overhead. This decision depends on the workload. Something that should be considered is that batch processing involves a fluctuating pattern that requires resource scaling. Real-time processing is more constant and predictable.If the business requirements allow, sending data in batches could reduce the energy as less data needs to be transmitted over the network due to reduced network overhead. Experimentation is required to measure whether this reduction in overhead has a significant effect on energy efficiency.
Participant
Cloud consumer
Related software artifact
Cloud workloads
Context
Public cloud
Software feature
Data processing
Tactic intent
Delaying data transport to allow batch processing, as opposed to continous real-time data transport and processing
Target quality attribute
Cost-effiency
Other related quality attributes
Energy-efficiency
Measured impact
< unknown >
Source
Master Thesis “Architectural Tactics to Optimize Software for Energy Efficiency in the Public Cloud” by Sophie VosGraphical representation
