Rediger

Del via


Networking considerations for sustainable workloads on Azure

Most workloads in the cloud rely heavily on networking to operate. Whether internal networking or public-facing workloads, the components and services used in provisioned solutions must consider the impact of carbon emissions. Consider that network equipment consumes electricity, including traffic between the data centers and end consumers. Learn about considerations and recommendations to enhance and optimize network efficiency to reduce unnecessary carbon emissions.

Internet traversal between data centers and end consumers is a significant Scope 3 emission. Therefore, recommendations in this section are aligned with the Principles of Green Software Networking area to improve networking efficiency.

Important

This article is part of the Azure Well-Architected sustainable workload series. If you aren't familiar with this series, we recommend you start with what is a sustainable workload?

Network efficiency

Reduce unnecessary network traffic and lower bandwidth requirements where possible, allowing for a more optimized network efficiency with less carbon emission.

Make use of a CDN

Unnecessary traffic on the network should be avoided, as it's a cause for extra carbon emissions.

Green Software Foundation alignment: Energy efficiency

Recommendation:

  • A CDN helps minimize latency through storing frequently read static data closer to consumers, and helps reduce the network traversal and server load.
  • Ensure to follow best practices for CDN.

Follow caching best practices

Minimizing the amount of data transferred is crucial.

Green Software Foundation alignment: Energy efficiency, Hardware efficiency

Recommendation:

  • Caching is a well-understood design technique to improve performance and efficiency.
  • A caching solution helps reduce network traversal and reduces the server load.
  • Consider that it may require tuning of parameters to maximize the benefit and minimize the carbon drawbacks. For example, setting a Time to Live (TTL).
  • Adding in-memory caching can help use idle compute resources, increasing the compute density of resources that are already allocated.
  • Read caching best practices.

Select Azure regions based on where the customer resides

The location of an application's consumers can be disparate, and it can be challenging to serve requests with good performance and energy efficiency if the distance is too great.

Green Software Foundation alignment: Energy efficiency

Recommendation:

Use managed audio and video streaming services with built-in compression

Applications making use of a media streaming service may have high requirements for bandwidth and compression, and can have a substantial carbon footprint if not designed carefully.

Green Software Foundation alignment: Hardware efficiency

Recommendation:

Enable network file compression

Networks sending uncompressed data can have a higher requirement on bandwidth, the allocated resources, and the solution in general. Consider compressing data to optimize the workload and design for a more network efficient solution.

Green Software Foundation alignment: Energy efficiency

Recommendation:

Maximize network utilization within the same cloud and region

Operating solutions in multiple regions have a networking impact. Network traversals between components in Azure are optimized to stay within the Azure infrastructure. However, any network traffic destined for the internet or a component in another cloud involves the public internet's router resources, which you have no control over regarding resource impact measurement or utilization.

Green Software Foundation alignment: Energy efficiency

Recommendation:

  • Keeping resources in a single cloud gives you maximum control and allows the cloud provider to optimize the network routing.
  • Maximize network utilization within the same cloud and, if possible, within the same region.
  • Since the cost can be a proxy for sustainability, review the Azure regions documentation in the Cost Optimization pillar of the Azure Well-Architected Framework.

Next step

Review the design considerations for storage.