Is it possible with dagster to force a schedule to call assets in a linear order even if they have no dependency on one another so maybe to avoid the situation where assets are called simultaneously so that it does not cause the db layer to fall over?

I've been successful in using

tag_concurrency_limits

and tagging my assets. I have a database table that is picky about reading and writing, even if it is different rows, so I have to limit the concurrency to 1 for that table. Any asset that is tagged that way, will wait until the available capacity and then materialize. There is also a tag

dagster/concurrency_key

that can play a similar role.