Sharing insights on technical analysis and exchange, making life better through technology.
This article reviews the main Redis deployment options—including single‑node, master‑slave with Sentinel, sharding via consistent hashing, and Redis Cluster—explaining their advantages, high‑availability mechanisms, scalability limits, and recommending suitable scenarios for each architecture.
This article compares three practical approaches—direct database storage, a Flink‑Kafka‑Redis‑Grafana pipeline, and an ELK stack—to achieve real‑time API request counting for high‑concurrency scenarios, outlining their architectures, advantages, and trade‑offs.
This article explains the technical mechanism behind WeChat's offline payment, detailing how a time‑based one‑time dynamic code is generated on the device, verified by the server, and destroyed to protect user accounts even without network connectivity.
The article explains why JVMs use generational garbage collection, how cross‑generation references cause missed objects during Minor GC, and how the card table together with write barriers and conditional marking dramatically reduces pause times and improves overall GC performance.
This article explains MySQL's redo log and binlog, why their write order can cause master‑slave inconsistencies, and how the two‑phase commit protocol atomically coordinates both logs to ensure reliable data consistency in distributed transactions.
This article explains how to design and implement a WeChat group red packet feature, covering database schema, non‑cached and cached workflows, concurrency control with Redis locks, and two allocation algorithms—random distribution and double‑average method.
This article examines three e‑commerce inventory deduction methods—order‑time, payment‑time, and pre‑deduction—detailing their mechanisms, advantages, drawbacks, and suitable scenarios to help developers choose the optimal strategy for high‑concurrency sales.
This article explains multiple database schema designs for hierarchical comment threads, compares their query performance, and shows how Redis can be used to sort hot comments and handle high‑concurrency likes, providing practical solutions for large‑scale comment systems.
Deploying new features without downtime can be challenging, but using blue‑green, canary (gray), and rolling release strategies lets teams switch traffic, control risk, and upgrade services gradually, each method offering distinct trade‑offs in cost, complexity, and compatibility handling.
Even with Nginx handling high‑performance load balancing and static content, a dedicated API gateway is essential for flexible routing, dynamic service discovery, fine‑grained traffic governance, and centralized business logic such as authentication and logging in microservice architectures.
