In this session we will walk through various techniques to significantly reduce the resource consumption of regular Spring Boot applications, including using Spring AOT for regular Spring apps, compiling Spring Boot apps to native images (using GraalVM), and using CRaC for instant startup (for scale-to-zero scenarios). We will compare the different approaches, discuss pros and cons for each technology, and share concrete numbers from real-world applications to give the audience an idea of what can be achieved using these technologies.

Target Audience: Developers, Architects
Prerequisites: Basic Spring Boot knowledge required
Level: Advanced

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/martin.lippert

User-centred design is one of the default modes of teams working with software, but the consequences are often unsustainable in a densely networked world as we privilege users over all other stakeholders and systems. How might teams approach building products, services and organisations from a more sustainable standpoint than 'user-centricity'? This talk looks at how the techniques of game design, community development, platform operations and security practices can support a practice focused on hyperobjects for multi-centric design.

Target Audience: Leaders, Builders, Architects, Designers, Community Members
Prerequisites: No previous knowledge, only enthusiasm for systems, building things and design
Level: Advanced

Extended Abstract:
The key feature of a 'tragedy' is when everybody does the right thing but it goes wrong anyway. The aim of this session will be to look at why user-centred design goes wrong even if everyone's intentions are pure. This talk (gently!) brings in ideas from feminism, design thinkers, political science and anthropology to focus on very practical, grounded approaches to sustainable design in software teams. We'll look at how building things and designing organisations that have increased levels of friction can improve users' experience and how 'seamless' design can lead to disempowerment. And we'll also draw on the speaker's practical experience of building products used by millions of citizens as part of the UK's digital transformation. By the end of the session we'll have a sense of what might replace the shallow seamlessness of 'user-centred' design — a multi-centric, transcendental design aimed at manufacturing enthusiastic consent.

"Which programming language is the fastest" usually is everyone's first thought when green software is mentioned! It's a common deduction that the fastest code is, therefore, the most efficient, which then, of course, can save us from this climate disaster. However, code efficiency is not even half of the story! In this talk, Sarah will review the three approaches that make software green. She will also introduce efficiency-achieving practices that can take us closer to fighting this pesky climate change.

Target Audience: Architects, Developers, SRE/DevOps
Prerequisites: Basic knowledge of any Programming Language, Introductory Familiarity with DevOps Space
Level: Basic

Extended Abstract:
In this talk, I will go over the following:

1. My journey so far with green software emphasizes how I don't need to leave my climate enthusiasm at home every day when I go to work
2. Brief facts about WHY we need to take action now in the tech industry
3. 3 approaches that make software green
4. Why code efficiency is not the answer to most green software problems with an example
5. Going over why DevOps practices are much more effective in achieving greenness in software with a couple of examples
6. Wrapping up with fruit for thoughts, especially highlighting the close connection between DevOps practices and Green Software practices
7. Encourage the audience to look at their software engineering problems through a green software lense

Expanding horizons has many facets. It means taking advantage of new opportunities that arise from technical progress, such as Large Language Models, or societal challenges like Sustainability. Expanding horizons also means taking responsibility. AI and data analytics have a direct impact on our future life, good and bad. Expanding horizons also means reflection on existing practice. We have perhaps forgotten the benefits of structured monoliths, or have sometimes overdone it with agility, which suggests a critical and learning retrospective.

Moderation: Frank Buschmann
Panelists: Isabel Bär, Zoe Lopez-Latorre, Carola Lilienthal, Xin Yao

Target Audience: Software Practitioners
Prerequisites: None
Level: Advanced

Extended Abstract:
The motto of OOP 2024 has many facets. Expanding horizons means understanding and taking advantage of new opportunities that arise from technological progress or societal challenges. For example, on Large Language Models, Sustainability, and the Metaverse. Expanding horizons also means taking responsibility and not blindly applying new technologies. For example, AI and data analytics have a direct impact on our future life and social interaction. With all the consequences, good and bad. But broadening horizons also means reflecting on existing technologies and practices. In the course of the euphoria about microservices, for example, we have perhaps forgotten the advantages of the structured monolith too much, or have sometimes overdone it with agility. A critical and learning retrospective seems appropriate.
In this panel, we will examine the various aspects of the motto of OOP 2024 to give us all meaningful guiding thoughts for the exciting journey to expanding our horizons.

This talk is about my journey as a Scrum Master towards creating sustainable DevOps teams. I will share my learnings and inspire the audience to raise awareness on sustainability in their own teams and organizations.
We will have a look at IT (and our own work) through the generational lens, to discover how long-term thinking can reshape the way we look at our daily work and help us find strategies for making IT sustainable.

Target Audience: Architects, Developers, IT Managers, Agile Professionals
Prerequisites: None
Level: Basic

Extended Abstract:
Climate change is a significant threat to the future of life on earth and as I was looking for ways to become more sustainable, the idea started to grow that at work, in my own DevOps teams, we could also take the sustainability perspective. I dove into the subject of sustainable IT and started with a ‘Planet as a Stakeholder Retrospective’ for my Scrum Team in which we went over the Principles of Green Software Engineering. We discussed what steps our team could take to reduce the carbon footprint of our services.
Taking the sustainability perspective was a new approach for the team, but everyone agreed on its importance. During that session, the team estimated that optimizing our landscape and decommissioning legacy components could reduce our footprint by a significant percentage!
Just imagine: what if all DevOps teams would do that? I started to give workshops about ‘the Planet as a Stakeholder’, in which I help teams to look at their IT services through the sustainability lens and let them define the first steps forward.
In this talk I will share my experiences: failures, challenges, successes, and examples of practical steps that teams have already taken to reduce their carbon footprint.

At Tchibo we wanted to reduce our server and energy consumption with our product development teams. But why would we care? We all like fast snappy development and test systems. And our shop needs to survive Black Friday’s shopping traffic. Annual Google Cloud consumption forecasts do not trigger us to consume less. But when we started to show teams their related carbon dioxide footprint, we created a feedback loop that will help us to become better CO₂-developers.
As developers, we have an impact - to program CO₂ reduction.

Target Audience: Everyone, Developers, DevOps People
Prerequisites: None
Level: Advanced

Extended Abstract:
We will present the idea and first measurements on the server side. The planned client side measurements are still work in progress and very difficult to perform. Nevertheless is the client side induced CO₂ consumption at large websites probably a large lever for reduction.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/johannes.mainusch