Django Tastypie atomic operation
I'd need to see:

The code making the API calls.
Any changes you've made to the resources.
What sort of stack this is deployed on.

If you happen to be using greenthreads, multiple workers, and/or multiple servers, it's possible the 2 requests are actually being processed out of order.
I strongly recommend changing your code to not perform concurrent actions on a remote resource; wait until one request is done before starting the next.
I am using Django 1.7.3 as my framework and Tastypie 0.11.1 as rest api library.
I have a basic model with name field and an api for creating this model.
My problem is with critical sections ( race conditions ) when trying to create the model.
I have tried transaction.atomic and set ATOMIC_REQUESTS = True on db level and yet when I am sending two requests as a race I receive two identical rows. 
Is there a way to ensure that Tastypie save function will be atomic ? or any way to ensure that requests will be atomic ?