Daobab DTO (Entity, Plate) objects are immutable. That means, the state cannot be modified and every modification creates a new object instance.
That means, objects are thread-safe as well.
Daobab is based into the stateless concept and by default does not contains an internal entity repository (although programmer may build it's own cache-targets). Database itself has the storage role.
In most cases, the immutable DTO concept is based on builders or all-arg constructors (like records).
Daobab works different. Everything is done in the background.
At the end, Daobab stores data into immutable Map.
Every modification, transparently creates a new immutableMap, contained the ordered change.
This approach work pretty efficient.