Garbage Collection GC in Modern Java Applications: GC Considerations for Microservices
summary
Microservices at Get Your Guide experience frequent out‑of‑memory crashes, latency spikes and retries traced to GC behavior: the search service hits failure when traffic exceeds 700 requests per second and switching to ZGC cuts tail latencies and pauses without extra CPU, while the inventory service stores huge 16‑month objects and needs G1GC for predictable collection. Clear metrics on GC frequency, pause durations and heap object sizes drive the decision and validate fixes.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:57Garbage collection in microservices
- 4:02Java GC fundamentals
- 6:51Java garbage collectors
- 7:12Search service latency issues
- 10:27Switching to ZGC
- 12:32Inventory service memory issues
- 15:42Choosing G1GC
- 16:27Lessons from failures
- 18:13Summary
related talks
41mCloud Chaos & Microservices Mayhem
41mBuilding Low Latency Microservices & Monoliths in Java
45mGo, Microservices and all the joy!
40mHigh-Performance Java-Cloud-Native Apps & Microservices
56mModern Java microservices in the Cloud!
51mResponsible Microservices
36mJava: Microservices...decisions, decisions, decisions everywhere
53mScaling Spring Boot Microservices
