bruin

Also it's lack of ingestion handling and VSCode/editor support, which it seems like Bruin considers very well!

And note that patents did not prevent it from bruin developed in the first place.

Currently, Bruin is meant as a single-node CLI tool that will do the orchestration and the execution within the same machine.

In the end, think of Bruin as a full pipeline/orchestrator, which would contain one or more assets using various other technologies.

Do you have integration for ML orchestration to reuse bruin inside our existing pipeline?

From a quick look, it seems like it could have replaced some of the orchestration code in Bruin to a certain extent.

It’s pretty remarkable what Bruin brings together into a single tool / workflow.

Do you have any particular example tools that you would compare Bruin in your mind that you would like to understand the difference better?

It looks like I can do this with Bruin but the documentation doesn't explicitly talk about single tenant vs multi-tenant design.

Your point on.bruin.yml documentation is spot on, and we’ll make improving that a priority.

I suspect that these laws have not been challenged under the bruin decision yet.

That being said, I tried starting the example bruin pipeline with duckdb on a current data project, and I'm having no luck getting the connection to appear with `bruin connections list` so nothing will run.

Bruin orchestrates individual runs for single pipelines, which means you can use any tool to schedule the runs outside and the assets will be orchestrated by Bruin.

In that sense, Bruin's alternative would be a stack rather than a single product.

What’s the equivalent of meltano’s (singer) taps in Bruin?