Durable Objects and silmutaneous registrations

[lkj4]

Just found this repo, looks pretty nice feature-wise!

The auth logic is using a DurableObject for in-memory locking of usernames when registering.
Avoid simultaneous registration with the same username!

Since you check if the username is unique why is this still a problem? And btw, are you really using Durable Objects here or just KV?

[g45t345rt]

The getData function is only using KV
It's from another package called cf-kvprefix and you can create managed indexes with it.
https://github.com/g45t345rt/cf-kvprefix

As for the username check
We have to check first if the username exists inside KV and make use of a DO to lock the value while registering.
KV is not synchronous and edge caching around the world takes a little bit of time to propagate data.
Storing a value in one instance and getting the value from another instance right away can return empty data