Ok. Thank you. Now our team needs to build something and try. Since the computing power is good for each instance it can probably run most of etl workloads.
Another question: each flight runs a separate instance? In case I run 2 flights in parallel, does MD handle write concurrency if it occurs? I mean, if the tasks refer to the same table/db.
So each flight runs a separate instance? In case I run 2 flights in parallel, does MD handle write concurrency if it occurs? I mean, if the tasks refer to the same table.
Currently, ducklake fully hosted by MD uses postgres catalog, correct? Considering the quack extension are there plans to use duckdb as catalog as well and if so, will it be a possibility for existing ducklakes in MD?
I have a ducklake fully hosted by MD. When I export a db to a local one am I charged by data egress like in S3 or only by computational resources by Motherduck?
.png){kind=logo}
