1 views collected around this technical thread.
This article explains how to build a robust offline inventory counting system that prevents data loss, resolves synchronization conflicts, and ensures seamless operation even when network connectivity is interrupted, offering practical design patterns and pitfall‑avoidance tips for warehouse teams.
This comprehensive guide covers core WMS terminology—from basic concepts like locations, storage slots, and SKUs to inbound/outbound processes, inventory management techniques such as FIFO and safety stock, strategic approaches including wave and picking methods, essential equipment like PDAs and RFID, and advanced industry jargon, providing product managers with the knowledge to navigate technical discussions, impress stakeholders, and optimize warehouse operations.
This guide walks you through creating and organizing Ansible inventory files, defining hosts and host groups, using nested groups and wildcards, understanding configuration file priority, and setting up a devops user with password‑less sudo and SSH keys to verify the setup.
The unified exchange mall middleware platform consolidates disparate points‑redemption and lottery flows into a four‑layer architecture—business, gameplay templates, domain models, and downstream services—offering standardized APIs, dynamic RPC routing, Redis‑based inventory control, anti‑fraud safeguards, and built‑in monitoring, thereby cutting development costs, enhancing maintainability, and ensuring system stability.
This article examines how delayed or inconsistent inventory synchronization leads to costly overselling and deadstock in e‑commerce, presents three destructive synchronization patterns, and offers a step‑by‑step guide—including real‑time messaging, distributed locks, rule‑engine integration, and intelligent alerts—to transform inventory management from a liability into a self‑healing system.
The article examines inventory pre‑reservation in e‑commerce, detailing performance challenges under high concurrency, and evaluates solutions such as asynchronous rate limiting, horizontal stock splitting, Redis caching, database transaction handling, deadlock avoidance, and data consistency mechanisms, highlighting a 24‑fold throughput increase.
The article analyzes the stability problems faced by an e‑commerce inventory platform—including complex workflows, data accuracy, database hotspots, and high‑frequency calculations—and details a series of backend engineering solutions such as traffic splitting, gray‑release links, Redis caching, consistency checks, async rate limiting, and comprehensive monitoring to improve reliability and performance.
This article analyzes the stability challenges faced by an e‑commerce inventory platform—including complex business flows, database hotspots, and high‑frequency calculations—and details a series of engineering solutions such as traffic splitting, gray‑release pipelines, Redis caching, consistency checks, throttling, and comprehensive monitoring to improve reliability and performance.
The article examines how frequent inventory adjustments in JD retail supply‑chain can suffer from concurrency issues, explains why traditional locking may fail, analyzes a real‑world case of lock misuse, and presents code‑level, database‑level, and architectural solutions to guarantee data consistency.
Ansible Inventory defines host lists and variables for automation; this guide explains its purpose, basic file format, verification commands, advanced grouping, variable settings, and privilege escalation techniques, providing practical code examples and tips to streamline server configuration and management.
This article compares three inventory deduction approaches—single‑field MySQL updates, sharded MySQL records, and Redis INCRBY with Lua scripting—analyzes their concurrency drawbacks, and provides a complete Java implementation using Redis Lua scripts, distributed locks, and callback‑based stock initialization.
This article explains how to implement product purchase quantity limits in a PHP‑based online store, covering database schema changes, modifications to product detail, cart, and checkout pages, Ajax‑driven updates, inventory checks, and order management to prevent overselling and improve user experience.
This article explains how to design the database, modify product detail, cart, and order pages, and use Ajax in PHP to enforce purchase quantity limits based on stock levels, ensuring accurate inventory management and improved user experience in online stores.
This article analyzes the problems encountered when constructing inventory pre‑reservation functionality—such as performance bottlenecks, thread‑synchronization, deadlocks, and data‑consistency issues—and presents a set of engineering solutions including async throttling, horizontal stock splitting, Redis caching, transaction‑based DB updates, lock ordering, and consistency‑verification mechanisms, with measured performance improvements.
This article explains several common technical solutions—locking queues, update‑statement limits, optimistic locking, temporary tables, and Redis pre‑stocking—to prevent inventory overselling, comparing their suitability for different concurrency levels and recommending the best approach for high‑traffic scenarios.
The article outlines the three‑step inventory deduction workflow—select, verify, update—and explains how concurrent requests can cause overselling, then compares mitigation strategies such as pessimistic SELECT FOR UPDATE locks, optimistic CAS version retries, atomic decrement SQL statements, and Redis transactions, highlighting their trade‑offs in consistency and throughput.
This article explains how to implement product purchase quantity limits in a PHP‑based online store by designing a stock field in the database, updating product detail, cart, and order pages, using Ajax for dynamic updates, and ensuring inventory consistency to improve user experience and operational efficiency.
This article details the evolution, layered architecture, stock types, deduction strategies, high‑concurrency solutions, and synchronization mechanisms of the Vivo Mall inventory system, illustrating how the backend was refactored to support diverse business scenarios and prevent overselling.
To handle exploding product inventory data, the company overhauled its warehouse inventory model by eliminating risky document‑hand‑offs, storing only changed rows instead of daily snapshots, and syncing transformed data to a data‑warehouse for reporting, which cut monthly accounting time by 30 hours (≈30 %), improved accuracy, enabled new analytics, and introduced TiDB migration and team upskilling.
The article explains how to mathematically balance inventory across multiple self‑operated big and cloud warehouses by calculating an ideal split ratio, allocating procurement, and recommending inter‑warehouse transfers—using a rule‑engine‑driven three‑service architecture that accounts for inbound/outbound flows, channel stocking, and cost‑efficiency to improve delivery performance.