Hotel Order Transaction System Architecture and Actor Framework Overview

Speaker Yu Xueping, a Java developer who joined Qunar in 2013, currently works on order transaction development within the large‑scale accommodation trading architecture.

The hotel order transaction architecture is fully event‑driven: a unified order‑store service persists changes and emits messages; each business system registers a QMQ listener to receive order change events, enabling more than 20 services to be driven by these events.

Key problems encountered include maintaining QMQ configurations for numerous listeners, handling message exceptions (e.g., frequent EditionConflictException due to optimistic locking), excessive coupling where a single message triggers multiple business logics leading to high retry costs, and fault scenarios where message backlog and retries overwhelm the system.

To address these issues, an Actor framework was created. Each business actor is bound to specific event types rather than raw QMQ messages, allowing independent execution units with their own retry strategies, persistent state, and isolated failure handling.

The framework provides a customizable retry mechanism (actors send delayed QMQ messages on failure without affecting other actors), fault‑recovery support via persisted execution logs (actor‑history.log, actor‑fail.log), and comprehensive monitoring and logging for each actor instance and overall order message processing.

Demo details include Spring configuration, the use of @QActor to register actors with the engine, @Qdiff to bind actors to particular order events, and example code snippets illustrating these annotations.

The presentation is part of Qunar’s internal technical carnival, aimed at sharing architectural insights and fostering cross‑team learning.