General
sync = true protects one JVM, not the cluster
0 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
PreviousSwitching from GPT-5.6 Sol to GPT-6 Astra: Start with Medium EffortNextSyncing your Obsidian
Related posts
Moving our warehouse off DuckDB
0Hacker News
Show HN: VHS Camera – Run your camera or videos through a simulated VHS signal
0Hacker News
Bitmovin (YC S15) Is Hiring Technical Graduates in Denver (Engineering/CS Focus)
0Hacker News
Device mockups and animated launch videos in your browser, no account needed.
0dev.to Design
Vellinko – Sign PDFs in the browser without uploading them
0Hacker News New
Show HN: Vivio House, an interactive 3D headquarters
0Hacker News New