Why Spring’s Bean Scanning Can Trigger Unresolvable Circular References (and How to Fix It)

This article examines how Spring Boot 2.0.3 resolves (or fails to resolve) setter‑based circular dependencies, explores bean definition scanning order, bean definition overriding, and instantiation sequence that can lead to an “unresolvable circular reference” error, and then shifts to explain ZGC’s mark‑compact algorithm, its evolution before and after JDK 16, and its performance characteristics.

bean-scanningcircular-dependencyjava-gc

0 likes · 14 min read

Why Spring’s Bean Scanning Can Trigger Unresolvable Circular References (and How to Fix It)

Tencent Cloud Developer

Aug 5, 2021 · Fundamentals

Java vs Go: A Comparative Analysis of Garbage Collection Algorithms

The article compares Java’s mature, generational garbage collector—using mark‑copy for young objects, mark‑sweep/compact for old, with sophisticated write barriers and fragmentation handling—to Go’s non‑generational, concurrent tri‑color mark‑sweep collector that relies on a span‑based memory pool, TCMalloc optimizations, and simpler root selection.

Garbage CollectionGenerational CollectionGo GC

0 likes · 14 min read

Java vs Go: A Comparative Analysis of Garbage Collection Algorithms

Alibaba Cloud Developer

Dec 20, 2019 · Operations

How We Traced a 48‑Hour Memory Leak in a Distributed Coordination Service

This article details a step‑by‑step investigation of repeated follower process alerts in a Paxos‑based distributed coordination service, revealing a Java GC pause‑induced memory leak in the front‑end Proxy and describing the rapid mitigation actions taken to restore system stability.

Distributed Systemsincident responsejava-gc

0 likes · 12 min read

How We Traced a 48‑Hour Memory Leak in a Distributed Coordination Service