title: Data modeling in snowflake
body: <p>We perform ELT in our company. we load the data to the landing zone (which is a database in snowflake) and have schemas as per the source from which it is retrieving the data such as:
  LZ(database) -- FACEBOOK&lt;LINKEDIN(schemas)
  (Here nothing needs to be changed)</p>
  <p>Once all the data is loaded, analysts create views/tasks to do the transformations as per the information needed.</p>
  <p>We are moving towards the domain-driven design in snowflake in later part. We have analysts and each analyst belongs to a domain such as sales, and vendor.</p>
  <p>We have identified all domains now next step is implementation. There are two ways:</p>
  <ol>
  <li>domains as databases</li>
  <li>domains as schemas inside a single database</li>
  </ol>
  <p>We can have a sales database, a vendor database.</p>
  <p>Or we can have a database such as analysts: inside which sales could be a schema and vendor could be a schema.</p>
  <p>Which one should I go for and why? I have seen in most cases its schemas only but what could work best and why and what could be the implications is what I am looking for</p>