How to handle concurrent access to a Scala collection?

Question

I have an Actor that - in its very essence - maintains a list of objects. It has three basic operations, an add, update and a remove (where sometimes the remove is called fr

Answer 1

You don't need to synchronize the state of the actors. The aim of the actors is to avoid tricky, error prone and hard to debug concurrent programming.

Actor model will ensure that the actor will consume messages one by one and that you will never have two thread consuming message for the same Actor.