TransactionDataStructureExample
From APIDesign
(Difference between revisions)
JaroslavTulach (Talk | contribs)
(New page: The code can be made even cleaner, if the internal data are kept in a special immutable object: <source lang="java"> import java.util.concurrent.atomic.AtomicReference; public abstrac...)
Next diff →
Revision as of 16:19, 6 June 2025
The code can be made even cleaner, if the internal data are kept in a special immutable object:
import java.util.concurrent.atomic.AtomicReference; public abstract class Helper { private static final class Data { final int value1; final int value2; final int value3; Data(int value1, int value2, int value3) { this.value1 = value1; this.value2 = value2; this.value3 = value3; } } private AtomicReference<Data> data = new AtomicReference<>(new Data(0, 0, 0)); protected abstract int combine(int x, int y); public final void update() { Data current; while (true) { current = data.get(); int r1 = combine(current.value1, current.value2); int r2 = combine(current.value2, current.value3); int r3 = combine(current.value3, current.value1); if (data.compareAndSet(current, new Data(r1, r2, r3))) { return; } } } }
Neat usage of immutability. The data that are supposed to be consistent are final in a Data class. The mutability is handled all at once with AtomicReference compareAndSet method. Either it fails and the computation runs again or it succeeds and atomically changes the data to newly created and consistent value. Let's call such this pattern TransactionalDataStructure.