Should one bother utilizing Promise.all within the context of a TypeORM transaction?

Question

Should one bother utilizing Promise.all within the context of a TypeORM transaction?

Using TypeORM to perform two operations in a single transaction with no specified order. Will utilizing Promise.all result in faster processing, or do the commands wait internally regardless?

Is there any discernible difference in efficiency between the two options?

// Option 1
getManager().transaction(async manager => {
  await Promise.all([
    manager.insert(...),
    manager.update(...),
  ]);
});;

// Option 2
getManager().transaction(async manager => {
  await manager.insert(...);
  await manager.update(...);
});

To clarify, I am aware of how Promise.all can enhance performance in JavaScript overall due to its single-threaded nature and event loop mechanics. However, my inquiry pertains specifically to the behavior of multiple queries within the same transactional manager in TypeORM, as they appear to execute sequentially whether Promise.all is used or not.

typescript typeorm

Answer 1

Answer №1

When dealing with concurrent transactions in Typeorm, using Promise.all may lead to incorrect behavior due to the fact that it doesn't wait for all promise results to complete.

await Promise.all(tenDbTxns);

// 5 out of 10 fulfilled
// 6 rejected ---> typeorm rollback 6 out of 10
// 4 pending and will be committed after fulfillment

To address this issue, consider the following solutions:

Execute queries sequentially:

const data = [];
for (const tx of tenDbTxns) {
    const res = await tx;

    data.push(tx);
}

Concurrent execution using Promise.allSettled which waits for all promise results:

const settled = await Promise.allSettled(tenDbTxns);
const data = [];
for (const res of settled) {
    if (res.status === 'rejected') {
        throw res.reason;
    }

    data.push(res.value);
}

Answer 2

When dealing with concurrent transactions in Typeorm, using Promise.all may lead to incorrect behavior due to the fact that it doesn't wait for all promise results to complete.

await Promise.all(tenDbTxns);

// 5 out of 10 fulfilled
// 6 rejected ---> typeorm rollback 6 out of 10
// 4 pending and will be committed after fulfillment

To address this issue, consider the following solutions:

Execute queries sequentially:

const data = [];
for (const tx of tenDbTxns) {
    const res = await tx;

    data.push(tx);
}

Concurrent execution using Promise.allSettled which waits for all promise results:

const settled = await Promise.allSettled(tenDbTxns);
const data = [];
for (const res of settled) {
    if (res.status === 'rejected') {
        throw res.reason;
    }

    data.push(res.value);
}

Answer 3

Answer №2

TypeORM streamlines your query creation process by generating queries for you, ultimately simplifying database interactions. For instance, when performing two separate actions on the database, it typically results in two queries being executed. Take, for example, creating a new customer and generating an invoice record. Utilizing promise all can help expedite this process, but it is essential to ensure that there are no interdependencies between the requests.

For instance, if creating an invoice requires information from a previously created customer, it's crucial to manage these dependencies effectively. However, with independent requests, promise all can be leveraged to execute multiple queries simultaneously. Afterward, you can verify the success of each request before committing the transaction or rolling it back accordingly.

I trust you will find this approach beneficial. If you have additional queries or require further assistance, kindly provide more context so I can offer tailored support.

Answer 4

TypeORM streamlines your query creation process by generating queries for you, ultimately simplifying database interactions. For instance, when performing two separate actions on the database, it typically results in two queries being executed. Take, for example, creating a new customer and generating an invoice record. Utilizing promise all can help expedite this process, but it is essential to ensure that there are no interdependencies between the requests.

For instance, if creating an invoice requires information from a previously created customer, it's crucial to manage these dependencies effectively. However, with independent requests, promise all can be leveraged to execute multiple queries simultaneously. Afterward, you can verify the success of each request before committing the transaction or rolling it back accordingly.

I trust you will find this approach beneficial. If you have additional queries or require further assistance, kindly provide more context so I can offer tailored support.

Answer 5

Answer №3

There is an issue with TypeOrm not functioning correctly when using promise.all and transactions (https://github.com/typeorm/typeorm/issues/1014). While using promise all may increase speed, transactions may not work as expected.

Answer 6

There is an issue with TypeOrm not functioning correctly when using promise.all and transactions (https://github.com/typeorm/typeorm/issues/1014). While using promise all may increase speed, transactions may not work as expected.

Should one bother utilizing Promise.all within the context of a TypeORM transaction?

Answer №1

Answer №2

Answer №3

Similar questions

Unable to declare a string enum in TypeScript because string is not compatible

A convenient utility for generating React components with pre-populated Tailwind CSS classes

Is there a method for verifying the application signature in Ionic?

Angular2 Navigation Menu

Angular TSLint: Proceed to the following stage despite any encountered errors

Error: Incorrect data type found in React Route component

Tips for integrating a variety of components onto a single webpage

Improprove the performance of an array of objects using JavaScript

What could be causing the module to break when my Angular service, which includes the httpClient, is added in the constructor?

Error: The jasmine framework is unable to locate the window object

Verify the validity of an image URL

Error in Typescript syntax within a CommonJS/Node module: Unexpected colon token found in function parameter

After upgrading from Angular 7 to 12, the module './rest.service.interface' does not export 'RestService' (imported as 'RestService'), causing it to not be found

Error message: Missing "@nestjs/platform-express" package when performing end-to-end testing on NestJS using Fastify

I am eager to perform DOM manipulation similar to jQuery but within the context of Angular 6

What is the method for obtaining a literal type through a function parameter to use as a computed property name?

When attempting to fetch JSON data using the Angular 2 `http.get()` method, the data returned is undefined and the component does not reflect any

What is the best way to incorporate a string value from an external file into a variable in TypeScript without compromising the integrity of special characters?

Exploring the functionality of angular reactive forms in creating intricate JSON structures

Why does the entire page in Next.JS get updated whenever I switch pages?