LSSUS03-BP02 Process data closer to source
Optimize data processing locations to minimize network usage and reduce energy consumption associated with data movement. Implement edge computing and hybrid architectures that process large datasets near their generation points, particularly for bandwidth-intensive applications like genomic sequencing and imaging workflows. Use managed services that provide optimized resource utilization and automatic scaling to reduce infrastructure overhead.
Desired outcome: Significantly reduce network bandwidth usage and associated energy consumption by processing data at optimal locations relative to data sources, while maintaining processing performance and regulatory requirements.
Common anti-patterns:
-
You transfer large datasets to centralized processing locations without considering network and energy costs.
-
You don't evaluate edge computing options for bandwidth-intensive research applications.
-
You process data in regions distant from data generation points without justification.
-
You don't consider data sovereignty and regulatory requirements when choosing processing locations.
-
You transfer raw data for processing instead of implementing preprocessing at the edge.
Benefits of establishing this best practice:
-
Reduce network bandwidth costs and energy consumption for large dataset processing.
-
Improve processing performance by reducing network latency for data-intensive operations.
-
Lower infrastructure costs through optimized resource utilization and managed service adoption.
-
Enhance data security and regulatory adherence by minimizing data movement across network boundaries.
-
Enable real-time processing capabilities for time-sensitive research applications.
-
Support hybrid and multi-cloud architectures that optimize for both performance and sustainability.
Level of risk exposed if this best practice is not established: Medium
Implementation guidance
Life sciences research generates massive datasets that traditionally require significant network resources to transfer to centralized processing locations. This approach is particularly inefficient for applications like genomic sequencing, cryo-electron microscopy, and high-resolution imaging where raw data volumes can reach terabytes per experiment. Processing data closer to its source reduces both network energy consumption and processing latency while often improving overall system performance.
Edge computing and hybrid architectures become essential when dealing with specialized equipment that generates large amounts of data continuously. For example, cryo-EM facilities, genomic sequencers, and imaging systems can benefit significantly from local preprocessing that reduces data volumes before cloud transfer. AWS services like AWS Outposts enable on-premises processing with cloud tools, while managed services provide automatic optimization without requiring dedicated infrastructure management.
Implementation steps
-
Analyze data generation patterns and processing requirements:
-
Map data sources and their typical output volumes and processing needs.
-
Identify bandwidth-intensive workflows that would benefit from edge processing.
-
Assess regulatory requirements for data processing locations.
-
Use and application discovery service to understand current data flow patterns.
-
-
Implement edge computing solutions for high-volume data sources:
-
Deploy edge compute solution such as AWS Outposts for on-premises processing of large genomic datasets.
-
Use AWS Snow Family devices for data processing in remote or bandwidth-constrained locations.
-
Implement IoT edge processing of sensor and instrument data.
-
Consider AWS Wavelength for ultra-low latency processing requirements.
-
-
Use managed services for optimized data processing:
-
Use services such as Amazon Kinesis Data Streams for real-time data processing and analytics.
-
Implement AWS Transfer Family for optimized file transfer and processing workflows.
-
Deploy AWS Batch at edge locations for containerized processing workloads.
-
Use Amazon SageMaker AI Edge for machine learning inference at data sources.
-
-
Optimize data preprocessing and filtering at source locations:
-
Implement data compression and filtering before cloud transfer.
-
Use AWS Lambda@Edge for lightweight data processing and transformation.
-
Deploy containerized preprocessing pipelines using Amazon ECS on AWS Outposts.
-
Implement quality control and data validation at source locations.
-
-
Monitor and optimize data movement and processing efficiency:
-
Track data transfer volumes and costs using FinOps tools such as Cloud Intelligence Dashboards.
-
Monitor processing performance and resource utilization with Amazon CloudWatch.
-
Use AWS X-Ray to trace data processing workflows and identify optimization opportunities.
-
Implement automated alerts for unusual data transfer patterns or processing inefficiencies.
-
Resources
Related best practices:
Related documents:
Related videos:
Related examples:
Related tools: