Volatile boolean vs AtomicBoolean

by

I use volatile fields when said field is ONLY UPDATED by its owner thread and the value is only read by other threads, you can think of it as a publish/subscribe scenario where there are many observers but only one publisher. However if those observers must perform some logic based on the value of the field and then push back a new value then I go with Atomic* vars or locks or synchronized blocks, whatever suits me best. In many concurrent scenarios it boils down to get the value, compare it with another one and update if necessary, hence the compareAndSet and getAndSet methods present in the Atomic* classes.

Check the JavaDocs of the java.util.concurrent.atomic package for a list of Atomic classes and an excellent explanation of how they work (just learned that they are lock-free, so they have an advantage over locks or synchronized blocks)

More Related Contents:

  1. Volatile vs Static in Java
  2. Is volatile expensive?
  3. Volatile variable in Java
  4. Simplest and understandable example of volatile keyword in Java
  5. Why doesn’t volatile in java 5+ ensure visibility from another thread?
  6. How to declare array elements volatile in Java?
  7. When is it preferable to use volatile boolean in Java rather than AtomicBoolean? [duplicate]
  8. Custom thread pool in Java 8 parallel stream
  9. Random errors when changing series using JFreeChart
  10. How to wait for all threads to finish, using ExecutorService?
  11. Is there an advantage to use a Synchronized Method instead of a Synchronized Block?
  12. Update JLabel every X seconds from ArrayList – Java
  13. When and how should I use a ThreadLocal variable?
  14. What is the difference between Thread.start() and Thread.run()?
  15. Practical uses for AtomicInteger
  16. Choosing the best concurrency list in Java [closed]
  17. Happens-before relationships with volatile fields and synchronized blocks in Java – and their impact on non-volatile variables?
  18. Servlet seems to handle multiple concurrent browser requests synchronously
  19. In Java, what are the boolean “order of operations”?
  20. Cleanest way to toggle a boolean variable in Java?
  21. Constructor synchronization in Java
  22. How can CopyOnWriteArrayList be thread-safe?
  23. Instruction reordering & happens-before relationship [duplicate]
  24. Memory barriers and coding style over a Java VM
  25. Are volatile variable ‘reads’ as fast as normal reads?
  26. Java socket swingWorker running but no message received or transmitted
  27. Uninitialized object leaked to another thread despite no code explicitly leaking it?
  28. Why boolean in Java takes only true or false? Why not 1 or 0 also?
  29. How does ConcurrentHashMap work internally?
  30. How to interrupt underlying execution of CompletableFuture

Leave a Comment