---
title: "Discussion on \"Promise.all() Is Not a Transaction: What Happens When One Promise Fails?\" | Hashnode"
description: "Discussion on \"Promise.all() Is Not a Transaction: What Happens When One Promise Fails?\". Learn why Promise.all() doesn't provide atomicity, cancellation, or rollback when concurrent operations fail."
url: "https://hashnode.com/posts/promise-all-vs-db-transaction/6aa27b455be87c3d90772a54"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Promise.all() Is Not a Transaction: What Happens When One Promise Fails?](https://iamgautam.hashnode.dev/promise-all-vs-db-transaction?utm_source=hashnode&utm_medium=feed)

Learn why Promise.all() doesn't provide atomicity, cancellation, or rollback when concurrent operations fail.

Sep 10 · 6 min read · iamgautam.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#concurrency](https://hashnode.com/tag/concurrency)
-   [#asyncawait](https://hashnode.com/tag/asyncawait)
-   [#promises](https://hashnode.com/tag/promises)
-   [#backend](https://hashnode.com/tag/backend)

## Written by

[Gautam Patel](https://hashnode.com/@iamgautam03)

@iamgautam03 · Surat, Gujarat, India

  
[View profile](https://hashnode.com/@iamgautam03)

A Developer with learnings in many different languages, frameworks and technologies.

I am a developer with learnings in many different languages, frameworks and technologies.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.