[nawitus]

Cconcurrent update of the same object is actually an extremely common real-life use case. You need to handle the arising conflicts anyway, so you might as well get the benefits of eventual consistency. If you don't have concurrent updates, then you don't have a distributed system. But that doesn't model the real world anymore. The state of the object is already distributed to multiple computers (e.g. mobile clients), and the database system needs to handle that.

You can, of course, handle the concurrency on the application level, but the question is, why bother? The database can help with managing that.