Focused on Java backend technologies, sharing fundamentals, multithreading, JVM, the Spring ecosystem, microservices, distributed systems, high concurrency, source‑code analysis, and practical experience. Continuously delivers high‑quality original content, interview guides, and learning roadmaps to help Java developers progress from beginner to advanced, enhancing technical skills and core competitiveness.
The article explains why common rate‑limiting approaches often break under high traffic, compares four mainstream algorithms, and provides a step‑by‑step guide to implement a lightweight, non‑intrusive single‑instance QPS limiter using Spring AOP and Guava's token‑bucket RateLimiter.
The article explains how to implement a zero‑intrusion, AOP‑based global API logging solution for Spring Boot applications, addressing common issues of manual logging such as code clutter, missing logs, inconsistent formats, privacy leaks, and performance overhead by using repeatable request wrappers, configurable filters, structured DTOs, asynchronous persistence, and comprehensive trace and desensitization utilities.
The article provides a step‑by‑step analysis of Spring AOP’s proxy creation process, explaining why some beans are proxied, how @Order, @EnableAspectJAutoProxy, proxyTargetClass and exposeProxy affect proxying, the differences between JDK and CGLIB proxies, and why private, static or final methods cannot be intercepted.
The article explains that Spring AOP cannot intercept methods marked as private, static, or final because JDK dynamic proxies only work on public interface methods and CGLIB subclasses cannot override such methods, leading to static matching but dynamic execution failure, self‑invocation bypass, and complete loss of advice for these method types.
When a Spring project uses more than two AOP aspects, the resulting multi‑layer nesting can cause sensitive data leaks, excessive logging, missed alerts, inconsistent responses, and random bugs; this article explains why ordering issues occur, how the onion model works, and provides concrete configuration strategies to achieve deterministic execution order.
This article explains why many Spring AOP pointcuts fail, clarifies the execution and @annotation expressions, details wildcard usage, presents dozens of concrete pointcut examples, compares their granularity and performance, and offers best‑practice tips to avoid common pitfalls in real‑world Java projects.
Spring AOP provides five distinct advice types—@Before, @AfterReturning, @AfterThrowing, @After, and @Around—each with specific execution timing; this guide explains their purposes, execution order, common pitfalls, and offers a complete SpringBoot example with code, Maven setup, and logging demonstrations.
Understanding the lifecycle, scope, and thread characteristics of HttpServletRequest and HttpSession reveals common misuse that leads to data corruption, login state errors, and lost cart data; the article explains core differences, proper use cases, real‑world bug examples, and practical solutions such as read‑only policies, synchronization, thread‑safe collections, and Redis‑based session storage.
Spring’s BeanPostProcessor is a global container hook that intercepts every bean’s lifecycle, enabling custom initialization, dynamic proxying, annotation processing, and resource cleanup; the article explains its three-tier hierarchy, execution order, priority rules, practical use‑cases like auto‑injection, logging, data masking, and common pitfalls.
The article explains why front‑end date and enum parameters often cause parsing errors in Spring applications, describes the two independent conversion mechanisms in Spring MVC and Jackson, and provides a step‑by‑step guide to building global custom converters that unify date formats and enum mappings across the whole project.
