I’m conceptualizing our migration from pre-release Dagster (solids, pipelines. Etc) to Dagster Cloud. Got a question I thought I’d pose to see what everyone’s thoughts are. When utilizing assets for EL, what are the pros and cons between creating assets dynamically based off say a config, versus explicitly defining each table individually as a asset? For example, if I have a PostgreSQL database with 30 tables I want to extract and load into Snowflake. I could dynamically create assets for each table, or specifically define each table as an asset. Even better yet, what approach would you take and why?

This really depends on what you’re trying to do. I’d recommend starting with a dynamic approach since that is simpler to maintain and minimal code, then you can switch to static if you need to start special-casing logic or config etc for specific assets.

Thanks Sean! It sounds like we got the right idea then.