Backend
sync = true protects one JVM, not the cluster
Bitan Sarkar Dev.to (EN Zone)
29 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
The benchmark everyone cited for "fastest backend" was archived in March, and the reason is the interesting part
Backend
56
Dev.to (EN Zone)
Finding Exoplanets in Noisy Data with Machine Learning
Backend
46
DEV Community
How to automatically find the batch size when using Accelerate with FSDP2? [D]
Backend
43
Reddit r/MachineLearning
Cross-Chain Bridge Risk Assessment: Aave V3
Backend
36
DEV Community
Comments0
No comments yet — be the first