[benblack]

Thanks for the comments, Jorge. What you describe as a fundamental flaw is perhaps better described as a careful engineering trade-off. AtomicMap is intended for specific use cases. If you are not dealing with an extremely high throughput, high concurrency write system, then AtomicMap may not be the right choice for you. If you are dealing with complicated write semantics that are likely to raise exceptions, AtomicMap may not be the right choice for you. In our application, we have a lot of threads writing at once. Exceptions in that path would indicate a pretty significant problem, far worse than how to handle them gracefully.

We have chosen to trade some flexibility in how the data structure can be used in exchange for an enormous increase in throughput. Your needs may differ, resulting in different trade offs.