Lufthansa Cargo · Enterprise & aviation
Engineering the rules behind cargo bookings
At Lufthansa Group, I combined hands-on engineering for Lufthansa Cargo with technical leadership for 15–20 engineers. My work spanned booking APIs, partner integrations, business rules, and production delivery.
- My role
- IT Consultant / Tech Lead
- Engagement
- Employment at Lufthansa Group
- Period
- 2022-2025
Enterprise delivery
Booking and integration services delivered through Lufthansa Group, with responsibility spanning implementation, technical guidance, and release support.
Project at a glance
- The need
- Cargo teams need booking and partner integrations that can accommodate changing business constraints without making every rule change an application-code concern.
- What I delivered
- Booking and integration services with versioned business rules, supported by release tooling and technical leadership that connects architecture to day-to-day delivery.
Delivered through Lufthansa Group. Internal systems and operational figures remain confidential.
Technical leadership · Lufthansa Group
Separating business rules from booking code
- The context
- Cargo bookings connect technical interfaces with frequently changing product, routing, and capacity constraints.
- My contribution
- I integrated Drools / Business Central with booking services and provided technical leadership for 15–20 engineers through architecture and code reviews, mentoring, and stakeholder alignment.
- The decision
- Separate changing business rules from API code so they can be versioned, tested, monitored, and rolled back when needed.
- The tradeoff
- A separate rules engine adds a service to operate. Clear contracts, compatible versions, tests, and rollback support are part of the solution, not follow-up work.
My contribution
- Developed booking APIs, offer qualification, and partner-message processing, translating cargo requirements into service behavior.
- Integrated Drools / Business Central so changing business rules could be versioned, tested, and released separately from API logic.
- Guided 15–20 engineers through architecture and code reviews, mentoring, stakeholder alignment, and delivery planning while continuing hands-on development.
- Supported production releases with Kubernetes, CI/CD, monitoring, logging, and Playwright end-to-end tests.
Technical challenge
A cargo booking brings together partner messages and changing product, routing, and capacity constraints. The engineering challenge was to accommodate that complexity while keeping service behavior testable and changes manageable across a team.
My approach
I built Java/Spring Boot and Node.js services, integrated EDI workflows, and separated decision logic with Drools / Business Central. Architecture reviews, end-to-end tests, and operational tooling connected those implementation choices to delivery.
Engineering decisions
Give business rules their own lifecycle
I separated rule changes from booking-service implementation with Drools / Business Central. Versioning, tests, and rollback support make decision logic easier to review without burying it in API code.
Treat operations as part of delivery
A service needs more than a working endpoint. I supported release automation, monitoring, logging, and end-to-end coverage so the team could deploy, diagnose, and maintain the software it delivered.
Explore the system architecture
Booking and partner workflows connect to integration services, which delegate business decisions to a dedicated rules layer. This conceptual view does not expose internal production topology.
System architecture
Select a component to explore its responsibilities.
Applications & partners: responsibilities
Technology
- Java
- Spring Boot
- TypeScript
- Vue
- Node.js
- Drools
- EDI
- Kubernetes
- Azure
- CI/CD