Cool Now we know that it is a good fit i

[storm sage]

seems like what you're trying to achieve is quite straightforward using the standard Dagger APIs. I don't think there's anything particular in the docs to check if you already have an idea about how Dagger works.

Still, don't hesitate to ping here if you have questions.

[thorn acorn]

@molten helm I'll send you friend request. Happy to set up some dedicated time to learn about your use case and help you get started.

[molten helm]

Hi Guys,
I'm excited to share that we've made significant progress by building a basic proof of concept (POC) utilizing Dagger for the image build process. It's been a rewarding experience so far. Now, we have an interesting question to ponder: Is it feasible to incorporate multiple Dagger engines into a single Node.js process? By doing so, we aim to dynamically scale the build process without the hassle of managing multiple backend instances

[storm sage]

Hey there! the SDK's currently don't have a way to connect to multiple different engines in the same process. Having said that, one possible workaround is to use Node's cluster module (https://nodejs.org/api/cluster.html) and spawn another node process to parallelize builds by setting the _EXPERIMENTAL_DAGGER_RUNNER_HOST variable as shown here (https://github.com/dagger/dagger/blob/main/core/docs/d7yxc-operator_manual.md)

LMK if that makes sense!