Travel services
One Broker Services
Backend development and data design for internal travel workflows connecting excursion providers, agency bookings, and tour packages.
My role
Backend developer and database-design contributor across Excursions and Tour Packages services.
Technology
- NestJS
- TypeScript
- Node.js
- PostgreSQL
- DynamoDB
- AWS Lambda
The challenge
Operators needed to search several travel services and create selected bookings in one workflow. Excursion provider data was stored as plain text even though provider rules and child-agency relationships affected bookings. That model needed to change without disrupting established behavior.
My contribution and the solution
I developed backend flows alongside a frontend developer, migrated provider data into an entity, updated database scripts and excursion workflows, implemented tour-price calculations and agency-chain bookings, and integrated excursions into package creation.
- Tour Packages coordinates selected services, with PostgreSQL for long-lived records and DynamoDB for short-lived creation state.
- Provider modeling and agency-chain booking creation preserve the required hierarchy and business rules.
- I moved the Tour Packages AWS Lambda runtime from Node.js 18 to 24 and adapted legacy functions to the newer runtime.
Delivery and outcome
I wrote extensive unit tests for Excursions, ran checks automatically before deployments, and validated changes with Postman and testing frontend deployments. I also supported releases and configuration review. The services were deployed in testing and production environments.
Provider-data and price-calculation issues were resolved through the migration and pricing work, based on direct validation and testing. No commercial metric is claimed.
Selected evidence
Public-facing screenshots, redacted views, or client-safe diagrams. Open an image for a closer look.
This privacy-first study uses diagrams only. It does not expose operators, travelers, bookings, prices, protected routes, or configuration.