Description of the impact of efficient coding on the planet. Using less ressource saves water, GHG and energy. Efficient UX also makes our world more sustainable. Linked to UNEP report on eWaste. Thanks @greenit.

1. @erichoresnyi#COIP21
So#ware
Eco-­‐Design
@StreamdataIO

2. @YourTwitterHandle#DVXFR14{session hashtag} @erichoresnyi#COIP21
Objectives
The
Art
of
Coding
is
about
balancing
UX,
performance,
and
resources
This
talk
does
not
cover
the
unlimited
benefits
of
coding
in
resource
management:
smart
grids,
ciDes,
transports…
This
talk
covers
the
impact
of
IT
resource
management
on
the
planet.

3. @erichoresnyi#COIP21
What
is
the
ICT
carbon
footprint?
Energy:
40
Nuclear
Plants
2x
France
Greenhouse
Gas
1/2
of
France
Water
consumpDon
1.5
France

4. @erichoresnyi#COIP21
What
makes
the
ICT
footprint
Make
=
2/3
Making
a
device
emits
100x
GHG
than
its
use
More
energy
used
than
during
lifeDme
Run
=
negligible
Dispose
≈
1/3

5. @erichoresnyi#COIP21
Logical
soluDon
Less Make è Less Impact !
BUT
Actually, desktop lifespan divided by 3 over the last 30
years !
Where is the catch ?

6. @erichoresnyi#COIP21
The
role
of
Bloatware
Electronic
lifespan
extends
BUT
latest
versions
cannot
run
Windows98-­‐Office97
è
Windows
8-­‐Office
114
more
RAM
needed
in
20
years
Web
pages
get
25%
fader
every
year

7. @erichoresnyi#COIP21
What
can
we
do
about
it
?
So#ware
Eco
Design
=
Efficiency:
Same
Performance,
Less
resources
in
RAM,
CPU,
Bandwidth
ê
Less
Make

8. @erichoresnyi#COIP21
Microso#
Bing
80%
energy
efficiency
by
removing
20%
of
search
results

9. @erichoresnyi#COIP21
Linkedin
MigraDon
to
node.js
=
Server
infrastructure
/
10
Efficiency
x112

10. @erichoresnyi#COIP21
Yahoo
vs
Google
ExhausDve
Vs
To-­‐the-­‐point
design
ê
/2
data
sent
+
/5
HTTP
requests
+
/3
CompleDon
Delay
(PLT)

11. @erichoresnyi#COIP21
SNCF
vs
Capitaine
Train
ExhausDve
vs
To-­‐the-­‐point
design
ê
/5
data
+
/20
HTTP
requests

12. @erichoresnyi#COIP21
PMU
vs
Betclic
TradiDonal
vs
PerDnent
design
ê
/5
Data
+
/2
TransacDon
Time
+
Challenger=Mobile
Leader

13. @erichoresnyi#COIP21
Waste
in
code
70%
features
are
never
or
rarely
used
ê
α-­‐
UX
-­‐
ω

14. @erichoresnyi#COIP21
Network-­‐Based
So#ware:
a
threat?
Data
per
device
grows
51%
per
year
X
Number
of
devices
increases
40%
a
year
X
Bandwidth
increases
19%
a
year
=
Network
impact
doubling
every
year

15. @erichoresnyi#COIP21
RESTful
API
=
sustainable
code
Network
Based
So#ware
=
SeparaDon
of
concern
client/server
Stateless
Cacheable
Layered
systems,
eg
proxies
Uniform
interface

16. @erichoresnyi#COIP21
Microservices
=
Be
Responsible
ComponenDzaDon
via
Services
Organized
around
Business
CapabiliDes
Products
not
Projects
Smart
endpoints
and
dumb
pipes
Decentralized
Governance
Decentralized
Data
Management
Infrastructure
AutomaDon
Design
for
failure
EvoluDonary
Design

17. @erichoresnyi#COIP21
Streaming
APIs
With
cache,
server
load
divided
by
x10
to
100
(facebook,
twider)
If
differenDal,
data
reduced
by
x10
to
100
on
top
Device
badery
consumpDon
divided
by
4

18. @erichoresnyi#COIP21
Key
Takeaways
ICT
impact
on
earth=40
nuclear
plants,
growing
x2
than
other
sector
Key
ICT
impact:
make
&
dispose
ê
Eco-­‐efficient
design
=
to-­‐the-­‐point

19. @erichoresnyi#COIP21
Credits
Research
by
F.Bordage
@greenit
Cisco
VNI:
y-­‐o-­‐y
data
growth
Masterpiece
of
architecture
:
R.Fielding,
REST
thesis
(2000)
Dinh&Boonkrong,
UniversityBangkok
InfoQ,
on
Linkedin
to
Node.js
MarDn
Fowler
@thoughtworks
on
microservices
Special
thanks
to
@vlavschneid,
@verseo_fr
and
the
@StreamdataIO
crew
for
supporDng
this
quest

20. @erichoresnyi#COIP21
Recos
Read
Fred’s
book
Monday
April
11th,
Assemblée
NaDonale
Paris,
prepare
#COIP,
Meetup
Come
to
EcoInfo
10th
year
day
April
23rd,
CNRS
Paris
16th
And
communicate
to
the
world
#COIP
D-­‐236
days
in
Paris
(too)

21. @erichoresnyi#COIP21
A#erword
Pix
are
mine
My
grandchildren
will
not
see
the
Guerande
saltmarsh,
Maurienne
glacier
and
Amsterdam;
unless
we
all
try
to
do
something
about
it
at
our
scale,
starDng
NOW