Agoda faced a significant issue with unwanted duplicate bookings being accidentally created due to system incidents and customer rebooking attempts. To mitigate this, Agoda introduced a booking deduplication feature that detects and prevents duplicate bookings.
As Agoda expanded its operations across multiple data centers and diversified its product offerings, the legacy booking deduplication system faced new challenges. The system could not detect duplicates when traffic was shifted between data centers, and maintaining separate deduplication services for each product type was complex.
Agoda addressed these challenges by:
The new booking deduplication system retrieves data from both local and central databases, combines the results, and processes the data to determine if a customer request is a duplicate booking. This approach ensures data integrity and redundancy, even in the event of database failures.
The system uses a single, generic table to accommodate all product types, making it highly scalable and easy to maintain. The table stores hashed static data for efficient exact matching and raw dynamic data in JSON format for flexible processing.
The booking deduplication service follows a four-step process: (1) retrieving and combining candidates from local and central databases, (2) filtering out candidates by status, (3) applying additional product-specific logic, and (4) reaching a conclusion on whether the request is a duplicate booking.
This new architecture has enabled Agoda to effectively manage duplicate bookings across its multi-data center infrastructure and diverse product offerings.
Vers une autre langue
à partir du contenu source
medium.com
Idées clés tirées de
by Agoda Engine... à medium.com 07-10-2024
https://medium.com/agoda-engineering/booking-deduplication-how-agoda-manages-duplicate-bookings-across-multiple-data-centers-08ddbe9e22f1Questions plus approfondies