DABs vs API
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 12:58 PM
DABs seem like a great way to build a project based workflow. However, I have a need to take a user's SQL and create a TABLE/VIEW based on it. We plan to use the API to submit the request but is this the best way going forward? Should we consider wrapping the user's SQL changes into a DAB and go through the creation this way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2024 06:07 PM
DABs use Terraform which in turn calls the API anyway. So, I guess it comes down to personal preference of deployment consistency, code maintenance etc. However, from your description of "taking a user's SQL" I'm assuming some sort of real-time application interface that takes the SQL query and builds assets. If so, I would go directly to the API instead of using DAB. If not and it is something about "productionizing" user's SQL queries in a programmatic manner, then DAB's with appropriate scheduled workflows/jobs is the way to go.
