This article compares Java's native record feature with the Lombok library, showing how records can reduce boilerplate code, outlining scenarios where records can replace Lombok, and discussing the limitations of each approach for clean and maintainable backend development.
This article presents Qunar Travel's "system slimming" project, describing how observability techniques, a two‑stage strategy, and automated tooling were used to identify and remove unused services and code, achieving a 50% reduction in code size, a 26% cut in services, and measurable improvements in reliability and release efficiency.
This article presents Qunar's comprehensive system slimming initiative, detailing the background of growing code bloat, the challenges of reducing millions of lines across thousands of services, the two‑phase plan for service and code pruning, the use of SA and other tooling to identify and safely delete unused resources, and the measurable outcomes such as nearly 50% code reduction, improved development speed, and future directions for further optimization.
The article explains how a C++‑based cross‑platform framework was built to unify iOS and Android implementations of WeChat Pay, reducing code size, improving crash stability, streamlining feature delivery, and addressing architectural issues such as inconsistent UI, poor scalability, and network request management.
