1 views collected around this technical thread.
This guide explains why Kafka message backlogs occur, how to diagnose bugs, optimize consumer logic, and use temporary topics for emergency scaling, while emphasizing monitoring, alerts, and proper offset handling to keep your streaming system healthy.
This article explains why message queues can become backlogged, identifies producer and consumer causes, and provides practical strategies—including adding consumers, increasing queue capacity, optimizing consumption logic, implementing failure handling, and rapid remediation steps—to quickly resolve backlog in production environments.
This article examines why message queues become backlogged—covering producer overload, broker persistence failures, and consumer bottlenecks—and outlines a step‑by‑step scaling and remediation strategy to restore smooth processing, including temporary queue expansion, load‑balanced forwarding, and post‑recovery cleanup.
This article explains how TCP full and half‑open connection queues work on Linux, why they overflow when the number of connections grows, and provides practical commands and kernel parameter adjustments such as backlog, somaxconn, and tcp_max_syn_backlog to resolve the issue.
The article examines the gap between the ideal of agile demand management—clear value‑driven goals, fast iterative releases, and unified backlogs—and the reality many teams face, then offers concrete principles, role guidelines, and decision‑making models to help product managers overcome common obstacles and achieve true demand agility.
This article outlines six practical metrics—unified backlog, user‑centric requirement description, consistent requirement flow, short lead time, high iteration completion rate, and stable iteration velocity—to help teams distinguish superficial agile ceremonies from truly effective agile execution.
This article explains why a low Redis memory fragmentation ratio is not necessarily caused by swap usage, demonstrates experiments with disabled swap and varying repl‑backlog‑size, and concludes that large replication buffers and small data sets can naturally produce ratios far below 1, which is normal.
This article presents a detailed case study of intermittent Dubbo connect‑timeout errors in a high‑concurrency deployment, describing step‑by‑step diagnostics—from port status checks and registry verification to TCP dump analysis—and explains how adjusting the server’s backlog and accept queue resolved the SYN‑drop issue.
The article uses the behind‑the‑scenes process of Friends Season 6 to illustrate agile concepts such as backlog, user stories, MVP, Scrum meetings and continuous delivery, showing how a sitcom’s production can serve as a model for effective R&D management.
The article discusses the challenges of allocating delivery team resources based on project budgets, the need for a monthly stakeholder "parliament" to prioritize demands, and the difficulty of creating a manageable, value‑driven backlog that balances large projects, regulatory work, and small initiatives.
This article compiles a series of Chinese-language resources on user story mapping, explaining how the technique helps agile teams create clearer backlog, prioritize features, and plan releases, offering both theoretical background and practical steps for effective implementation.
The article explains how to construct a user story map, organize activities and tasks, prioritize features using a spine-and-rib metaphor, and leverage the map for planning, testing, and communication throughout product development, offering practical guidance for agile teams and product managers.
The article explains why flat user‑story backlogs are ineffective, illustrates the problems with prioritizing and planning using such lists, and shows how constructing a user‑story map provides context, improves backlog management, and enables better release planning for product development.
The article recounts a hands‑on Beijing Agile Community workshop on User Story Mapping, explains the technique’s role in solving common agile requirement‑analysis problems, describes its structure and how it connects to backlog and release planning, and shares personal reflections on its usefulness for product management.
The article explains how architects can adopt a risk‑ and cost‑driven, lightweight approach to keep architecture agile, offering five actionable recommendations—decision‑focused delivery, a backlog of architectural concerns, economic impact prioritization, minimal architecture, and delivering just enough expectations—applicable across agile and plan‑driven projects.