From f12b83ec5c58b94c5efbc510a2bfff8a4f0f5c7c Mon Sep 17 00:00:00 2001 From: Thomas Wilkerling Date: Wed, 21 May 2025 19:38:15 +0200 Subject: [PATCH] add async resolver readme --- doc/resolver-consecutive.svg | 3 +++ doc/resolver-parallel.svg | 3 +++ doc/resolver.md | 18 ++++++++++++++++++ 3 files changed, 24 insertions(+) create mode 100644 doc/resolver-consecutive.svg create mode 100644 doc/resolver-parallel.svg diff --git a/doc/resolver-consecutive.svg b/doc/resolver-consecutive.svg new file mode 100644 index 0000000..ad46251 --- /dev/null +++ b/doc/resolver-consecutive.svg @@ -0,0 +1,3 @@ + + +
Resolver
Resolver
DB
DB
NOT
NOT
Result
Result
AND
AND
OR
OR
NOT
NOT
Resolve
Resolve
OR
OR
AND
AND \ No newline at end of file diff --git a/doc/resolver-parallel.svg b/doc/resolver-parallel.svg new file mode 100644 index 0000000..3632630 --- /dev/null +++ b/doc/resolver-parallel.svg @@ -0,0 +1,3 @@ + + +
Resolver
Resolver
DB
DB
NOT
NOT
Result
Result
AND
AND
OR
OR
NOT
NOT
Resolve
Resolve
OR
OR
AND
AND \ No newline at end of file diff --git a/doc/resolver.md b/doc/resolver.md index 787e8f3..0d9b76d 100644 --- a/doc/resolver.md +++ b/doc/resolver.md @@ -162,6 +162,8 @@ const result = new Resolver({ .resolve(100); ``` +## Async Resolver + ### Using Async Queries (incl. Runtime Balancer) All async tasks will run in parallel, balanced by the runtime observer: @@ -208,6 +210,22 @@ const resolver = await new Resolver({ When tasks are processed consecutively, it will skip specific resolver stages when there is no result expected. +### Compare Parallel VS. Consecutive + +When using the parallel workflow, all resolver stages will send their requests (including nested tasks) to the DB immediately and calculate the results in the right order as soon as the request resolves. When the overall workload of your applications has some free resources, a parallel request workflow improves performance compared to the consecutive counterpart. + +

+ +

+ +--- + +When using the consecutive workflow, all resolver stages will send their requests (including nested tasks) to the DB only when the previous request resolves. The advantage of this variant is when a stage becomes invalid because of the previous result, it can skip the request completely and continue with the next stage. This can reduce the overall workload. + +

+ +

+