Backend
sync = true protects one JVM, not the cluster
Bitan Sarkar Dev.to (EN Zone)
2 views
Originally published at bitsar.net.
Twelve pods, one Redis, and @Cacheable(sync = true) on the method. I read that as a protected endpoint. It coordinates callers inside one JVM, so a cold key was still twelve calls to the same slow dependency. This is what I found when I went looking for the clustered version of that annotation, why I think it does not exist, and what it took to build one.
Source, benchmarks, the full parameter guide and nine open issues: github.com/BitanSarkar/coalesce-java.
Read original: https://dev.to/bitan_sarkar/sync-true-protects-one-jvm-not-the-cluster-16m0
← Previous
My negative test stopped being negative when a config file grew by four rows
Next →
4,768 LLM Runs, Zero Lost Sweeps: Hardening a Field-Test Runner for Timeouts, Hangs, and Cost
Related
If the Remainder Doesn't Shrink, It's a Zero: A Bootcamp Lab on Agent Loop Progress
Backend
1
Dev.to (EN Zone)
Snapshot Exit, Stdout, and Stderr Before One Flag Extract
Backend
2
Dev.to (EN Zone)
Azure Function App Stuck on "Runtime Unreachable"? How VNet Integration and Private Endpoints Fixed It
Backend
2
DEV Community
Cross-Chain Bridge Risk Assessment: Tether Gold
Backend
1
DEV Community
Comments0
No comments yet — be the first