<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: DABs vs API in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/dabs-vs-api/m-p/87667#M1712</link>
    <description>&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Tue, 03 Sep 2024 01:07:32 GMT</pubDate>
    <dc:creator>Shazaamzaa</dc:creator>
    <dc:date>2024-09-03T01:07:32Z</dc:date>
    <item>
      <title>DABs vs API</title>
      <link>https://community.databricks.com/t5/administration-architecture/dabs-vs-api/m-p/83681#M1618</link>
      <description>&lt;P&gt;DABs seem like a great way to build a project based workflow.&amp;nbsp; However, I have a need to take a user's SQL and create a TABLE/VIEW based on it.&amp;nbsp; We plan to use the API to submit the request but is this the best way going forward?&amp;nbsp; Should we consider wrapping the user's SQL changes into a DAB and go through the creation this way?&lt;/P&gt;</description>
      <pubDate>Tue, 20 Aug 2024 19:58:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dabs-vs-api/m-p/83681#M1618</guid>
      <dc:creator>jlowe</dc:creator>
      <dc:date>2024-08-20T19:58:33Z</dc:date>
    </item>
    <item>
      <title>Re: DABs vs API</title>
      <link>https://community.databricks.com/t5/administration-architecture/dabs-vs-api/m-p/87667#M1712</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Sep 2024 01:07:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/dabs-vs-api/m-p/87667#M1712</guid>
      <dc:creator>Shazaamzaa</dc:creator>
      <dc:date>2024-09-03T01:07:32Z</dc:date>
    </item>
  </channel>
</rss>

