Former senior tech manager at Meituan, ex‑tech director at New Oriental, with experience at JD.com and Qunar; specializes in Java interview coaching and regularly shares hardcore technical content. Runs a video channel of the same name.
Although JWT is marketed as a decentralized, stateless solution, the majority of real‑world applications still rely on a Token + Redis approach because it simplifies logout handling, avoids Redis outages, and aligns better with practical security requirements.
When interviewers ask about MySQL InnoDB vs MyISAM, go beyond transaction support and discuss six deeper differences—including count(*) performance, MVCC, storage layout, caching, crash recovery, and ideal use cases—to showcase comprehensive technical knowledge.
Redis does not instantly release memory for expired keys; instead it employs three deletion strategies—timed, periodic, and lazy—to balance memory usage, CPU load, and data accuracy, with periodic scans optimized by random sampling and time limits.
This article explains how HTTP's stateless nature leads to the use of cookies, sessions, tokens, and JWTs for authentication, comparing their mechanisms, security trade‑offs, and practical interaction flows with clear diagrams.
Token expiration can be handled with three main strategies—frontend‑driven periodic refresh, backend sliding‑window renewal, and the industry‑standard double‑token (access + refresh) scheme—each balancing implementation simplicity, user experience, and security, with the double‑token approach offering the most robust solution.
This article explains how Nacos continues to provide configuration reads and service calls after its server crashes, details its long‑polling mechanism for dynamic updates, describes where configuration data is stored, compares the CAP trade‑offs for service discovery versus configuration management, and clarifies why Nacos implements both Distro and Raft protocols.
This article reveals five common MySQL pitfalls—including uncontrolled InnoDB lock granularity, low default IOPS, misleading VARCHAR length handling, undersized InnoDB Buffer Pool, and a fragile Buffer Pool LRU algorithm—and offers practical configuration tips to prevent performance degradation.
This article explains how to import a hundred‑million‑row Excel dataset into MySQL by using CSV format, streaming parsers like EasyExcel, batch inserts, asynchronous processing, and partial‑transaction strategies to ensure feasibility, data integrity, and high performance.
This article presents nine practical techniques—including Thread.join, CompletableFuture, CountDownLatch, CyclicBarrier, Semaphore, single‑thread executor, ReentrantLock with Condition, Phaser, and BlockingQueue—to reliably enforce a specific execution sequence among Java threads, a frequent interview challenge.
This article breaks down seven common thread‑pool pitfalls frequently asked in Java interviews, explains core‑thread reclamation, warm‑up, pool states, task‑completion checks, the risks of the default ForkJoinPool, and when to use single, fixed, or cached thread‑pool executors.
