Speaker
Abstract
What makes a platform efficient? Is it how quickly code executes, or is it how quickly developers can use it to solve problems? Quarkus makes both people and hardware more efficient. That’s cool, but how does it work? Usually, we expect to trade-off developer experience against runtime efficiency. In this session, Holly will dive into some of the technical underpinnings of Quarkus’s efficiency. She’ll give advice for those using or considering Quarkus - should you be doing reactive programming? Do native binaries run fastest? She’ll also share general principles and transferrable discoveries from the engineering team, such as knowing what you’re optimising for, avoiding cache pollution, and how to be static-but-dynamic.
Interview
I’m a senior principal software engineer, helping to build Quarkus. I’m focussed especially on the community of people and companies who are extending the Quarkus ecosystem, and also on the sustainability of Quarkus.
The Quarkus team have made so many good engineering decisions, especially in the area of efficiency, I want to share them with the wider technology space. There are a lot of lessons in what Quarkus have done that can be applied to all sorts of areas.
The target audience has two parts; one is people who are using, or considering using, Quarkus, and want to know a bit more about what’s under the hood. The second group is people who maybe aren’t looking at Quarkus, but who are looking at making their systems more efficient.
For people who’re not using Quarkus, I’m hoping they’re able to steal a whole bunch of ideas and techniques and best practices from seeing what Quarkus has done. These might enable them to make better use of hardware or be more performant, but they might also improve the team’s human efficiency; after all, people are in general, the most expensive ingredient in a development project. For people considering Quarkus, I hope they get a better understanding of all the ways Quarkus can help them and also understand the ‘why’ behind some of the design decisions.
I just love QCon and always get so much out of the sessions, I’m struggling to think of just one thing!
Topics
QCon London 2024 is a three day conference for senior software engineers, architects and team leads. An international program committee of working engineers selects every session. Patterns and practices, not products and pitches.
From the same track
Tuesday 9 April
10:35 Mountbatten (6th Fl.) Session high performance What Can You Learn From the Fastest Code in the World? Alan Elder Principle Software Engineering Manager @Microsoft One of the challenges in the cloud is handling the vast amount of data that has to be sent and received. Doing this in software reduces the need for specialist hardware and increases flexibility. That's why superfast data planes exist. 11:45 Mountbatten (6th Fl.) Session Rust Not Just Memory Safety: How Rust Helps Maintain Efficient Software Pietro Albini Technical Lead of Ferrocene @Ferrous Systems, Formerly on the Rust Core Team, and Previous Lead of the Rust Infrastructure Team Rust's claim to fame is its memory safety without compromising on performance, eliminating whole classes of security vulnerabilities and bringing systems programming to the new generation. 13:35 Mountbatten (6th Fl.) Session ebpf Unleashing the Kernel With eBPF Liz Rice Chief Open Source Officer @Isovalent at Cisco, Ex-Governing Board at CNCF and OpenUK, Emeritus Chair, CNCF Technical Oversight Committee, eBPF, Security, Cilium, Cloud Native eBPF is a kernel technology that is enabling a new generation of high-performance, low-overhead tools for networking, security and observability. 14:45 Rutherford (4th Fl.) Unconference Unconference: Efficient Programming Languages An unconference is a participant-driven meeting. Attendees come together, bringing their challenges and relying on the experience and know-how of their peers for solutions. 15:55 Mountbatten (6th Fl.) Session Quarkus Zero Waste, Radical Magic, and Italian Graft – Quarkus Efficiency Secrets Holly Cummins Senior Technical Staff Member, Quarkus Team @IBM, Java Champion, Previously Senior Principal Software Engineer, Quarkus @Red Hat What makes a platform efficient? Is it how quickly code executes, or is it how quickly developers can use it to solve problems? Quarkus makes both people and hardware more efficient. That’s cool, but how does it work? 17:05 Windsor (5th Fl.) Session WebAssembly Turbocharged Development: The Speed and Efficiency of WebAssembly Danielle Lancashire Principal Software Engineer @Fermyon, Kubernetes Maintainer The **software carbon intensity (SCI)** of an application is the sum of its operational emissions and embodied hardware emissions. Serverless, or functions as a service (FaaS), provides a path towards reducing operational emissions by running event-driven applications only as needed.