Travel Tech Booking Engine Modernization
Large North-American Travel Tech Booking Engine Modernization
Large North-American Travel Tech Booking Engine Modernization
Large North-American Travel Tech Booking Engine Modernization
An enterprise-scale leisure travel marketplace connecting travel agents with leisure-focused travel suppliers, facilitating research, marketing, and selling of vacations in the USA and Canada.
An enterprise-scale leisure travel marketplace connecting travel agents with leisure-focused travel suppliers, facilitating research, marketing, and selling of vacations in the USA and Canada.
An enterprise-scale leisure travel marketplace connecting travel agents with leisure-focused travel suppliers, facilitating research, marketing, and selling of vacations in the USA and Canada.
Microservices
AWS
Cloud
Client
Client
NDA
NDA
NDA
Date
Date
2017-2020
2017-2020
2017-2020
Role
Role
Development partner
Development partner
Development partner
Website
Website
NDA
NDA
NDA
Travel Tech Booking Engine Modernization
Travel Tech Booking Engine Modernization
Travel Tech Booking Engine Modernization
Challenge
Challenge
Challenge
Our client’s Travel Booking Engine has been built in 1990s-2000s, and it included integrations Sabre Global Distribution System based on legacy cryptic interface. The operational cost of keeping legacy integrations alive has exceeded 6M USD annually (4.5M infrastructure cost: proprietary on-prem farm and 2 HP Tandem mainframes + 1.6M personnel cost, which included the development team and trained department of Travel Agents).
Client’s decision was to migrate to modern Sabre Orchestrated APIs. Usage of modern services greatly increases content and offering of Flights represented to client’s customers. Most important, migration to modern GDS APIs allows to decommission costly legacy infrastructure and repurpose teams maintaining the old technology.
Our client’s Travel Booking Engine has been built in 1990s-2000s, and it included integrations Sabre Global Distribution System based on legacy cryptic interface. The operational cost of keeping legacy integrations alive has exceeded 6M USD annually (4.5M infrastructure cost: proprietary on-prem farm and 2 HP Tandem mainframes + 1.6M personnel cost, which included the development team and trained department of Travel Agents).
Client’s decision was to migrate to modern Sabre Orchestrated APIs. Usage of modern services greatly increases content and offering of Flights represented to client’s customers. Most important, migration to modern GDS APIs allows to decommission costly legacy infrastructure and repurpose teams maintaining the old technology.
Our client’s Travel Booking Engine has been built in 1990s-2000s, and it included integrations Sabre Global Distribution System based on legacy cryptic interface. The operational cost of keeping legacy integrations alive has exceeded 6M USD annually (4.5M infrastructure cost: proprietary on-prem farm and 2 HP Tandem mainframes + 1.6M personnel cost, which included the development team and trained department of Travel Agents).
Client’s decision was to migrate to modern Sabre Orchestrated APIs. Usage of modern services greatly increases content and offering of Flights represented to client’s customers. Most important, migration to modern GDS APIs allows to decommission costly legacy infrastructure and repurpose teams maintaining the old technology.
Solution delivery
Solution delivery
Solution delivery
Brightgrove's team has delivered the migration to the new set of Sabre APIs. Migration was executed in 2 phases:
Search-to-Book functionality migration and Post-Purchase functionality migration. Each phase included detailed requirement creation, architecture solution design, software development and validation, user acceptance testing and actual production roll-out.
Brightgrove's team has delivered the migration to the new set of Sabre APIs. Migration was executed in 2 phases:
Search-to-Book functionality migration and Post-Purchase functionality migration. Each phase included detailed requirement creation, architecture solution design, software development and validation, user acceptance testing and actual production roll-out.
Brightgrove's team has delivered the migration to the new set of Sabre APIs. Migration was executed in 2 phases:
Search-to-Book functionality migration and Post-Purchase functionality migration. Each phase included detailed requirement creation, architecture solution design, software development and validation, user acceptance testing and actual production roll-out.
The requirement creation process involved mapping legacy services to orchestrated APIs, compiling parameterization tables to ensure backward compatibility, creating custom request sequences to replicate platform workflows, building Postman libraries for the development team, and generating technical documentation in the form of epics and user stories.
The requirement creation process involved mapping legacy services to orchestrated APIs, compiling parameterization tables to ensure backward compatibility, creating custom request sequences to replicate platform workflows, building Postman libraries for the development team, and generating technical documentation in the form of epics and user stories.
The requirement creation process involved mapping legacy services to orchestrated APIs, compiling parameterization tables to ensure backward compatibility, creating custom request sequences to replicate platform workflows, building Postman libraries for the development team, and generating technical documentation in the form of epics and user stories.
The architecture solution design phase involved evaluating volume and load requirements for the upgraded integration, selecting and justifying the architectural approach, estimating infrastructure costs and needs, and obtaining CTO approval for the proposed architecture.
The architecture solution design phase involved evaluating volume and load requirements for the upgraded integration, selecting and justifying the architectural approach, estimating infrastructure costs and needs, and obtaining CTO approval for the proposed architecture.
The architecture solution design phase involved evaluating volume and load requirements for the upgraded integration, selecting and justifying the architectural approach, estimating infrastructure costs and needs, and obtaining CTO approval for the proposed architecture.
The software development process involved implementing functionality based on the defined requirements, establishing QA processes and validation procedures, and delivering the developed functionality to the UAT team.
The software development process involved implementing functionality based on the defined requirements, establishing QA processes and validation procedures, and delivering the developed functionality to the UAT team.
The software development process involved implementing functionality based on the defined requirements, establishing QA processes and validation procedures, and delivering the developed functionality to the UAT team.
During user acceptance testing, the selected UAT team validated functionality against real production configurations and use cases. Brightgrove's Product Owner collected feedback and converted it into additional requirements, and the development team implemented the resulting change requests.
During user acceptance testing, the selected UAT team validated functionality against real production configurations and use cases. Brightgrove's Product Owner collected feedback and converted it into additional requirements, and the development team implemented the resulting change requests.
During user acceptance testing, the selected UAT team validated functionality against real production configurations and use cases. Brightgrove's Product Owner collected feedback and converted it into additional requirements, and the development team implemented the resulting change requests.
The production roll-out followed a "gradual legacy replacement" strategy, starting with 0% traffic on the new services and gradually scaling up to 75% over 30 days. A 60-day period of 24/7 proactive care with defined SLAs was established, and the final switch to 100% traffic occurred after 45 days.
The production roll-out followed a "gradual legacy replacement" strategy, starting with 0% traffic on the new services and gradually scaling up to 75% over 30 days. A 60-day period of 24/7 proactive care with defined SLAs was established, and the final switch to 100% traffic occurred after 45 days.
The production roll-out followed a "gradual legacy replacement" strategy, starting with 0% traffic on the new services and gradually scaling up to 75% over 30 days. A 60-day period of 24/7 proactive care with defined SLAs was established, and the final switch to 100% traffic occurred after 45 days.
Results we delivered
Results we delivered
Results we delivered
30% infrastructure cost reduction after first year of initial release
65% infrastructure cost reduction starting from the second year after release
Reduced load on Travel Agents department by 25%
Increased unit economics of booked Sabre flights by ~6% via richer flight content
Attracted new customers for a total of ~20k annual flight bookings via extended Fare Class options
Technology Partnership Impact
Technology Partnership Impact
Technology Partnership Impact
Brightgrove's partnership has enabled our client to:
• Significantly reduce OPEX costs
• Maintain high product quality standards
• Unlock new feature development
• Obtain new clients
• Build a business case for future integration upgrades
Brightgrove's partnership has enabled our client to:
• Significantly reduce OPEX costs
• Maintain high product quality standards
• Unlock new feature development
• Obtain new clients
• Build a business case for future integration upgrades
Brightgrove's partnership has enabled our client to:
• Significantly reduce OPEX costs
• Maintain high product quality standards
• Unlock new feature development
• Obtain new clients
• Build a business case for future integration upgrades
Download extended case study in .pdf
Download extended case study in .pdf