In every project's lifecycle, there arises a defining moment, a critical juncture where one must confront the monstrous spectre of technical debt.
In this instance, the project's fate teeters on the precipice of choice.
In our newest release of Eclipse Kura 5.3.0 we silently swapped out our old networking stack to one based on NetworkManager, all while maintaining feature parity. This decision did not come lightly.
We, courageous souls, dared to challenge our technical debt, and want to tell you about our journey.
Objective of the presentation:
Join us at our session, where we will unravel the intricacies and limitations of our old networking stack. Discover the motivation behind our decision to change it and the technical challenges we overcame to make it possible. We will go deep into the weeds about our API modifications, demonstrating how we maintained feature parity from a user and API perspective. We will talk about the impacts on performance, discuss our plans for the future and most importantly, we will answer the burning question on everyone's mind:
Was it worth it?
Attendee pre-requisites - If none, enter "N/A":
N/A
