Applying refactoring techniques to improve environmental impact of a software application

The current EU climate regulations force the companies to make their carbon footprint transparent. This makes determining the carbon footprint coming from digital services or software applications even more important. There are two important aspects to analyse here:
- understanding how to measure carbon footprint of a software solution
- understanding the importance of reducing the carbon footprint and providing software developers possibilities how to quickly make these reductions possible.

On this session I would like to talk about the impact that refactoring techniques have on the carbon footprint of a software application.
Key points of the session are:
- providing a methodology how to measure carbon footprint of a software running on cloud or on a process level. Here I would also focus on the challenges that measuring the carbon footprint has.
- providing an overview of different refactoring techniques and their environmental impact e.g when refactoring for SOLID principles.

Requirements engineering as basis for architecting a green software

When we think of making software more sustainable, we often jump straight to efficient code or green hosting. But what if the biggest leverage lies much earlier, even before a single line of code is written?

Requirements Engineering is our first opportunity to shape software in ways that reduce energy consumption, extend hardware lifespan, and minimize unnecessary functionality. By embedding sustainability into our requirements, we can guide design, architecture, and development decisions that favor greener outcomes.

In this session, you will get to know practical tips how you can construct your requirements engineering process and workshops with your stakeholders and use that information to achieve an energy efficient software solution.

Deep dive: how to measure carbon footprint of a microservice architecture

In this session I would like to provide insights on state of the art solutions on how to measure carbon footprint of a software solution.

Content of the session will include:
- introduction to why it is important to be able to track emissions of a software solution
- challenges that we face as an industry that make theses measurements difficult
- what metrics are used
- and what tools and processes are currently present in the state of the art that enable measuring and tracking carbon footprint of software applications in a microservice architecture.

Content of this talk will be showing a live demo and insights from measuring the carbon footprint of a microservice architecture.

Business value of environmental friendly software architecture

Designing environmentally friendly software architectures often meets hesitation from stakeholders, usually because the cost benefits are unclear, teams feel unprepared to build sustainably and early estimations tend to inflate the perceived effort and expense. This session sheds light on why sustainable architecture is not only feasible but often financially advantageous. Through concrete examples, we’ll explore how greener design choices can reduce (and occasionally increase) infrastructure and software costs, and why understanding these trade-offs gives teams and organizations a competitive edge. Furthermore results from case studies, that compare sustainable practices to non-sustainable design, will be presented to the audience.

When trying to convince stakeholders or customers into incorporating carbon footprint measurements into the software we are building, the costs of it have a significant importance on providing arguments. Attendees of the session can expect to have a clear overview on how different decisions impact each other and the costs of running and maintaining software.

This session will provide practical examples of how different environmental friendly design choices impact the costs of the infrastructure and a running software.

Bridging the gap between environmental friendly software practices, research and leadership

From past conferences and networking with colleagues, what I have noticed is that there is an increased interest into incorporating environmental friendly software practices in software projects. The challenges faced are mostly related to not knowing how to target sustainability work in software and how to convince leadership to support this.

This talk will be focused on exactly that: introducing techniques and ideas on how to fill the gap between the software community, researchers and management. Using team topologies concepts, we would deep dive into building a facilitator team within a company to support their fellow developers on the transition to writing more environmental friendly software.

The ideal situation would be a close collaboration between all parties to support creating environmental friendly software