Sustainability is a lens through which the public has started scrutinising various industries. This lens is slowly increasing its focus on the field of IT. As software architects we are uniquely equipped to see this coming and be at the forefront of change.
During this talk, the audience is invited ...
Sustainability is a lens through which the public has started scrutinising various industries. This lens is slowly increasing its focus on the field of IT. As software architects we are uniquely equipped to see this coming and be at the forefront of change.
During this talk, the audience is invited to test its knowledge on the energy usage of various common devices. This surprises most audiences and creates awareness about the need to collect data before we can effectively design new solutions.
Current efforts and organisations working towards greener IT are introduced and compared, as well as how anyone can join in these efforts.
At the end of this talk, the audience has been inspired to be critical about the way we design software systems and (cloud) infrastructures, invited to remain critical on decisions made in existing and new projects and they will leave with a hopeful sense of new possibilities.
Size: 12.98 MB
Language: en
Added: Oct 08, 2024
Slides: 82 pages
Slide Content
ARCHITECTING A SUSTAINABLE FUTURE
Jan-Hendrik Kuperus (@jhkuperus)
1
THERE IS NO TIME TO WASTE
2
3
4
5
— Lord Kelvin, Institution of Civil Engineers, 1883
" When you can measure what you are speaking about, and
express it in numbers, you know something about it; but when
you cannot measure it, when you cannot express it in numbers,
your knowledge is of a meagre and unsatisfactory kind."
6
LET'S TEST YOUR INTUITION...
7
TEST YOUR INTUITION...
100
• "Standard Refrigerator"
• Energy Consumption Index:
▪ Total Energy Consumed in 1 year
▪ Typical Usage in Household of 4
▪ Refrigerator is set as 100
8
HIGHER OR LOWER?
100
9
HIGHER OR LOWER?
100 51
9.1
HIGHER OR LOWER?
100
10
HIGHER OR LOWER?
100 1111
10.1
HIGHER OR LOWER?
100
11
HIGHER OR LOWER?
100 124
11.1
HIGHER OR LOWER?
100
12
HIGHER OR LOWER?
100 192
12.1
HIGHER OR LOWER?
192
13
HIGHER OR LOWER?
192
533
13.1
HIGHER OR LOWER?
192
533
133
13.2
HIGHER OR LOWER?
192
533
133 75
13.3
HIGHER OR LOWER?
192
533
133 75
TOTAL WIFI SETUP: 1065 (~€123/YR)
13.4
DOES SUSTAINABILITY IN IT MATTER?
• Datacenters emit ~1% of Global CO emissions (IEA)
2
15.1
DOES SUSTAINABILITY IN IT MATTER?
• Datacenters emit ~1% of Global CO emissions (IEA)
2
• Datacenters consume ~1-1.5% of Global Energy (IEA)
15.2
DOES SUSTAINABILITY IN IT MATTER?
• Datacenters emit ~1% of Global CO emissions (IEA)
2
• Datacenters consume ~1-1.5% of Global Energy (IEA)
• Networking consumes another ~1-1.5% of Global Energy (IEA)
15.3
DOES SUSTAINABILITY IN IT MATTER?
• Datacenters emit ~1% of Global CO emissions (IEA)
2
• Datacenters consume ~1-1.5% of Global Energy (IEA)
• Networking consumes another ~1-1.5% of Global Energy (IEA)
• Ye a r l y g r o w t h was estimated at 20%-40%
15.4
DOES SUSTAINABILITY IN IT MATTER?
• Datacenters emit ~1% of Global CO emissions (IEA)
2
• Datacenters consume ~1-1.5% of Global Energy (IEA)
• Networking consumes another ~1-1.5% of Global Energy (IEA)
• Ye a r l y g r o w t h was estimated at 20%-40%
• Current estimates see AI pushing Datacenters to 20% of Global
Energy in 2030 (PGIM)
15.5
YES, OUR CHOICES MATTER
16
SO WHAT CAN WE DO?
17
18
JOIN THE GREEN SOFTWARE FOUNDATION
BECOME A GSF CHAMPION (LIKE ME ! )
19
20
WE MUST IMPLY CONSTRAINTS ON OURSELVES
21
WE MUST IMPLY CONSTRAINTS ON OURSELVES
• The Cloud has made us lazy
21.1
WE MUST IMPLY CONSTRAINTS ON OURSELVES
• The Cloud has made us lazy
• Infrastructure feels "Infinite"
21.2
WE MUST IMPLY CONSTRAINTS ON OURSELVES
• The Cloud has made us lazy
• Infrastructure feels "Infinite"
▪ It's a victim of Parkinson's Law of Triviality
21.3
— Biz Stone, Co-Founder of Twitter
"Constraints Inspire Creativity"
22
LET'S GET PRACTICAL
23
LET'S GET PRACTICAL
• Observability is key
23.1
LET'S GET PRACTICAL
• Observability is key
▪ Include Carbon Intensity
23.2
LET'S GET PRACTICAL
• Observability is key
▪ Include Carbon Intensity
• Implement Demand Shaping
23.3
LET'S GET PRACTICAL
• Observability is key
▪ Include Carbon Intensity
• Implement Demand Shaping
• Implement Demand Shifting
23.4
LET'S GET PRACTICAL
• Observability is key
▪ Include Carbon Intensity
• Implement Demand Shaping
• Implement Demand Shifting
• Calculate Software Carbon Intensity
23.5
LET'S GET PRACTICAL
• Observability is key
▪ Include Carbon Intensity
• Implement Demand Shaping
• Implement Demand Shifting
• Calculate Software Carbon Intensity
• Implement LightSwitchOps
23.6
OBSERVABILITY
24
OBSERVABILITY
• You cannot improve what you don't measure
24.1
OBSERVABILITY
• You cannot improve what you don't measure
• Measuring CO directly is very hard
2
24.2
OBSERVABILITY
• You cannot improve what you don't measure
• Measuring CO directly is very hard
2
• Proxies are available: Cost, Utilisation, Resource Counting
24.3
OBSERVABILITY
• You cannot improve what you don't measure
• Measuring CO directly is very hard
2
• Proxies are available: Cost, Utilisation, Resource Counting
▪ Libraries like CO2.js give you a starting point
24.4
OBSERVABILITY
• You cannot improve what you don't measure
• Measuring CO directly is very hard
2
• Proxies are available: Cost, Utilisation, Resource Counting
▪ Libraries like CO2.js give you a starting point
• Including Carbon Intensity
24.5
25
IMPLEMENT DEMAND SHAPING
26
IMPLEMENT DEMAND SHAPING
• The false need to do everything right now
26.1
IMPLEMENT DEMAND SHAPING
• The false need to do everything right now
• Can workloads be moved to other times?
26.2
IMPLEMENT DEMAND SHAPING
• The false need to do everything right now
• Can workloads be moved to other times?
• Rethink the nightly CI/CD builds?
26.3
IMPLEMENT DEMAND SHAPING
• The false need to do everything right now
• Can workloads be moved to other times?
• Rethink the nightly CI/CD builds?
• Plan batches in low Carbon time slots
26.4
IMPLEMENT DEMAND SHIFTING
27
IMPLEMENT DEMAND SHIFTING
• Carbon Intensity is available for many
countries
27.1
IMPLEMENT DEMAND SHIFTING
• Carbon Intensity is available for many
countries
• Move a heavy workload to a "greener"
region
27.2
CARBON AWARE SOFTWARE
• Automate Demand Shaping/Shifting
• Software that decides on its own
28.2
CARBON AWARE SOFTWARE
• Automate Demand Shaping/Shifting
• Software that decides on its own
• Ultimate Maturity Level for Green
Software
28.3
CARBON AWARE SOFTWARE
• Automate Demand Shaping/Shifting
• Software that decides on its own
• Ultimate Maturity Level for Green
Software
• (GSF: Carbon SDK)
28.4
29
CALCULATE SOFTWARE CARBON INTENSITY
• ISO has accepted SCI as a standard
• Yields a metric for a single software product
• Allows comparison of changes in the product
• Not suitable for comparing products
30
LIGHSWITCHOPS
31
LIGHSWITCHOPS
• Scaling Infrastructure to Zero
31.1
LIGHSWITCHOPS
• Scaling Infrastructure to Zero
• Are your OTA-environments always on?
31.2
LIGHSWITCHOPS
• Scaling Infrastructure to Zero
• Are your OTA-environments always on?
▪ Be honest "
31.3
LIGHSWITCHOPS
• Scaling Infrastructure to Zero
• Are your OTA-environments always on?
▪ Be honest "
▪ Savings could be close to 50%
31.4
LIGHSWITCHOPS
• Scaling Infrastructure to Zero
• Are your OTA-environments always on?
▪ Be honest "
▪ Savings could be close to 50%
• 40% of developers is afraid of Scaling to
Ze r o
31.5
LIGHSWITCHOPS
• Scaling Infrastructure to Zero
• Are your OTA-environments always on?
▪ Be honest "
▪ Savings could be close to 50%
• 40% of developers is afraid of Scaling to
Ze r o
• 50% of developers say their project scales
manually
31.6
LIGHSWITCHOPS
• Scaling Infrastructure to Zero
• Are your OTA-environments always on?
▪ Be honest "
▪ Savings could be close to 50%
• 40% of developers is afraid of Scaling to
Ze r o
• 50% of developers say their project scales
manually
• 6.5% of developers say their project
Scales to Zero
31.7
WRAPPING UP
32
WRAPPING UP
1. Get Informed
32.1
WRAPPING UP
1. Get Informed
2. Start a Community
32.2
WRAPPING UP
1. Get Informed
2. Start a Community
3. Run Assessment Tools
32.3
WRAPPING UP
1. Get Informed
2. Start a Community
3. Run Assessment Tools
4. Monitor for Idle & Overprovisioned Resources
32.4
WRAPPING UP
1. Get Informed
2. Start a Community
3. Run Assessment Tools
4. Monitor for Idle & Overprovisioned Resources
5. Upgrade Languages & Frameworks
32.5
DO NOT HESITATE TO ASK FOR HELP!
Jan-Hendrik Kuperus
Green Software Foundation Champion
Architecting a Sustainable Future
@jhkuperus
www.yoink.nl
33