Transaction System Best Practices: Event‑Driven Architecture, Document Model, and Availability Guarantees

During a summer “Code Talk” session, Qunar’s accommodation trading system technical lead Chen Congwu shared best practices for building robust transaction systems, emphasizing the importance of event‑driven architecture, flexible document models, and comprehensive availability safeguards.

The talk began with a light‑hearted introduction and a brief award ceremony for contributors to the previous Baidu Waimai technical newsletter.

1. Event‑Driven Architecture

Key points included system decoupling for better extensibility, process segmentation for reusability, readability, and maintainability, unified order‑change event emission, an event execution engine, and visualizing event dependencies.

2. Document Model

The speaker highlighted a flexible schema that allows zero‑cost table structure changes, easy extensibility, and a customizable search engine to adapt to evolving business requirements.

3. Availability Guarantees

Techniques discussed were circuit breaking and rate limiting, gray‑release strategies, pre‑warming, automated testing tools, risk mitigation during system refactoring, and asynchronous transformation to improve system resilience.

Images illustrating the concepts were displayed throughout the session.

The Q&A segment featured active participation from attendees, with additional questions from the host’s colleague, followed by a lively discussion after the presentation.

The recap concluded with a thank‑you note, a reminder to follow the Baidu Waimai technology team’s public account, and a short promotional banner.