Optimizar proceso de creación/actualización de usuarios y resolver race condition #271
+35
−45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Este PR aborda un problema crítico de race condition en la creación de usuarios y mejora significativamente el performance general de nuestro sistema de gestión de usuarios.
Problema actual:
Actualmente, cuando se realizan múltiples llamadas concurrentes a endpoints autenticados (por ejemplo, usando
await Promise.all([...])
) para un usuario que se está autenticando por primera vez, puede ocurrir una race condition. Esto resulta en un error de clave duplicada:Este error se produce porque múltiples procesos intentan crear el mismo usuario simultáneamente, violando la restricción de unicidad en el email.
Cambios propuestos:
Reemplazar
updateUserProfileInfo
conupsertUserProfileInfo
:Implementar una operación upsert utilizando
onConflictDoUpdate
:Beneficios: