If two connections are trying to create the same record, how will aerospike ensure that only one of them will be able to execute successfully? Aerospike maintains a queue for the operations on a single record. So if a record exists all the operations on that record can execute serially. But what will happen if there is a create operation being called by multiple connections?
As you said, since Aerospike serializes transactions, if the create only client policy is used (for example, in java, the recordExistsAction), the second one will fail, but by default, the second "create" would be treated as an update...