Danh sách bài viết đã xuất bản.
A client sends an order request, the server completes it, but the response is lost in transit. The client sees only a timeout and retries. If the API creates another order or charges the card twice, the fault lies in server design, not in the client's reasonable retry behavior.
Read more →
Rate limiting is not only for blocking bots. It protects databases and dependencies from bursts, distributes resources fairly between tenants, controls API costs, and helps a system degrade predictably under load. A poorly designed limiter can instead block thousands of legitimate users behind NAT or become a new single point of failure.
Read more →
Creating an order commonly requires two writes: persist the order in a database and publish an OrderCreated event to a broker. If the database commits and publishing fails, inventory and email services never learn about the order. If publishing succeeds before the transaction rolls back, consumers process an order that does not exist. This is the dual-write problem.
Read more →
A website working when you manually open it does not mean it has been healthy all day. Regional DNS failures, expiring TLS certificates, incorrect API responses, or intermittent servers can continue for hours without proactive monitoring. Uptime Kuma is a self-hosted tool for periodic service checks, notifications, and status pages without building a full observability platform.
Read more →
The difficult part of moving WordPress is not copying files; it is avoiding lost orders, comments, or content created during the move. A reliable migration needs a rollback path, tests on the new server before DNS changes, and control over the period when both servers exist.
Read more →
A successful ALTER TABLE does not automatically make a deployment safe. In production, old and new application versions commonly overlap for minutes or longer. A migration that locks a table, renames a column immediately, or backfills millions of rows in one transaction can increase latency, exhaust the connection pool, and make rollback impossible.
Read more →
You are halfway through a feature when production suddenly needs a hotfix. The familiar response is to stash your changes, switch branches, fix the issue, and restore the original workspace. That becomes awkward when many files are uncommitted, dependencies are running, and the IDE already holds valuable context. git worktree solves this by giving one repository multiple working directories, each with its own checked-out branch.
Read more →
A transaction is more than wrapping several SQL statements in BEGIN and COMMIT. When requests concurrently read and modify data, an application must choose an isolation level, lock the correct rows, keep transactions short, and deliberately retry concurrency failures.
Read more →
RISC‑V is an open-standard Instruction Set Architecture (ISA) based on RISC principles. It defines the language software uses to communicate with a processor: instructions, registers, privilege modes, and extensions. RISC‑V is not one CPU design, a chip manufacturer, or a promise that every related implementation is open source.
Read more →
High “used” RAM on Linux does not automatically mean memory exhaustion. The kernel uses idle RAM for page cache and can reclaim it for applications. A real incident appears when MemAvailable remains low, swapping becomes active, processes stall, or the kernel invokes the OOM Killer.
Read more →