Event-driven backend for business-critical aviation software

Situation. AVIOBOOK builds business-critical software that pilots use before and during flight operations. I worked for AVIOBOOK across two periods. In 2022 I maintained and extended both the legacy platform (WildFly) and the cloud-native platform, and supported the migration to containerised deployments.

In 2024 I returned as lead backend developer: the application for tracking aircraft defects was due for replacement, and a technical assessment led to the decision to rewrite it entirely.

The techlog is a legally mandated document under EASA regulations: recording and follow-up of defects must be fully traceable and auditable. Those requirements shaped the data model and the reliability guarantees of the new backend.

Approach. For the rewrite of the “techlog” application I took on the role of lead backend developer and helped define the architecture and implementation strategy for the new backend.

In concrete terms:

• A technical assessment of the existing application, with the rewrite as its outcome;
• Contributing to the architecture and implementation strategy for a cloud-ready, event-driven backend for aircraft defect tracking;
• Technical analysis, ticket refinement and setting development standards;
• Integrations over RabbitMQ with MRO systems such as IFS Maintenix;
• Guiding and coaching the backend developers, working closely with the architect, analyst and stakeholders;
• Following up on the load tests and resolving performance issues where needed.

Result. A cloud-ready, event-driven backend for aircraft defect tracking, with an architecture and development standards the team builds on.