Built site for gh-pages

.nojekyll

@@ -1 +1 @@
-0547ae6e
+1b0d0ab1

chapters/sec1/1-2-proj-arch.html

@@ -462,7 +462,7 @@ <h2 data-number="2.1" class="anchored" data-anchor-id="choose-the-right-presenta
 </ol>
 <p>Choosing the right type of presentation layer will make it much easier to design the rest of your project. Here are some guidelines on how to choose which to use.</p>
 <p>If the results of your software are for machine-to-machine use, you’re thinking about a job or API. You should create a job if it runs in a batched way, i.e.&nbsp;you write a data file or results into a database. If you want results to be queried in real-time, it’s an API.</p>
-<p>If your project is for humans to consume, you’re thinking about creating an app or report, depending on whether you need a live Python or R process on the back-end.</p>
+<p>If your project is for humans to consume, you’re thinking about creating an app or report. Reports are great if you don’t need to do data processing that depends on user input and apps are great if you do.</p>
 <p>This flow chart illustrates how I think about which of the four things to build.</p>
 <p><img src="images/presentation-layer.png" class="img-fluid" alt="A flow chart of choosing an App, Report, API, or Job for the presentation layer as described in this section." width="600"></p>
 </section>

search.json

@@ -137,7 +137,7 @@
     "href": "chapters/sec1/1-2-proj-arch.html#choose-the-right-presentation-layer",
     "title": "2  Data Project Architecture",
     "section": "2.1 Choose the right presentation layer",
-    "text": "2.1 Choose the right presentation layer\nThe presentation layer is the thing that will be consumed by your users. You need to start by figuring out the details of your presentation layer because a lot of the data flows for your project will be dictated by your presentation layer choices.\nBasically all data science projects fall into the following categories.\n\nA job. A job matters because it changes something in another system. It might move data around, build a model, or produce plots, graphs, or numbers to be used in a Microsoft Office report.\nFrequently, jobs are written in a SQL-based pipelining tool (dbt has been quickly rising in popularity) or in a .R or .py script.1 Depending on your organization, the people who write jobs in your organization may be called data engineers.\nAn app. Data science apps are created in frameworks like Shiny (R or Python), Dash (Python), or Streamlit (Python). In contrast to general purpose web apps, which are for all sorts of purposes, data science web apps are usually used to give non-coders a way to explore data sets and see data insights.\nA report. Reports are code you’re turning into an output you care about – like a paper, book, presentation, or website. Reports are the result of rendering an R Markdown doc, Quarto doc, or Jupyter Notebook for people to consume on their computer, in print, or in a presentation. These docs may be completely static (this book is a Quarto doc) or they may have some interactive elements.2\nAn API (application programming interface). An API is for machine-to-machine communication. In general purpose software, APIs are the backbone of how two distinct pieces of software communicate. In the data science world, APIs are most often used to provide data feeds and on-demand predictions from machine learning models.\n\nChoosing the right type of presentation layer will make it much easier to design the rest of your project. Here are some guidelines on how to choose which to use.\nIf the results of your software are for machine-to-machine use, you’re thinking about a job or API. You should create a job if it runs in a batched way, i.e. you write a data file or results into a database. If you want results to be queried in real-time, it’s an API.\nIf your project is for humans to consume, you’re thinking about creating an app or report, depending on whether you need a live Python or R process on the back-end.\nThis flow chart illustrates how I think about which of the four things to build."
+    "text": "2.1 Choose the right presentation layer\nThe presentation layer is the thing that will be consumed by your users. You need to start by figuring out the details of your presentation layer because a lot of the data flows for your project will be dictated by your presentation layer choices.\nBasically all data science projects fall into the following categories.\n\nA job. A job matters because it changes something in another system. It might move data around, build a model, or produce plots, graphs, or numbers to be used in a Microsoft Office report.\nFrequently, jobs are written in a SQL-based pipelining tool (dbt has been quickly rising in popularity) or in a .R or .py script.1 Depending on your organization, the people who write jobs in your organization may be called data engineers.\nAn app. Data science apps are created in frameworks like Shiny (R or Python), Dash (Python), or Streamlit (Python). In contrast to general purpose web apps, which are for all sorts of purposes, data science web apps are usually used to give non-coders a way to explore data sets and see data insights.\nA report. Reports are code you’re turning into an output you care about – like a paper, book, presentation, or website. Reports are the result of rendering an R Markdown doc, Quarto doc, or Jupyter Notebook for people to consume on their computer, in print, or in a presentation. These docs may be completely static (this book is a Quarto doc) or they may have some interactive elements.2\nAn API (application programming interface). An API is for machine-to-machine communication. In general purpose software, APIs are the backbone of how two distinct pieces of software communicate. In the data science world, APIs are most often used to provide data feeds and on-demand predictions from machine learning models.\n\nChoosing the right type of presentation layer will make it much easier to design the rest of your project. Here are some guidelines on how to choose which to use.\nIf the results of your software are for machine-to-machine use, you’re thinking about a job or API. You should create a job if it runs in a batched way, i.e. you write a data file or results into a database. If you want results to be queried in real-time, it’s an API.\nIf your project is for humans to consume, you’re thinking about creating an app or report. Reports are great if you don’t need to do data processing that depends on user input and apps are great if you do.\nThis flow chart illustrates how I think about which of the four things to build."
   },
   {
     "objectID": "chapters/sec1/1-2-proj-arch.html#do-less-in-the-presentation-layer",

sitemap.xml

@@ -2,110 +2,110 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
   <url>
     <loc>https://do4ds.com/index.html</loc>
-    <lastmod>2023-10-05T16:00:12.127Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.287Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/intro.html</loc>
-    <lastmod>2023-10-05T16:00:12.139Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.295Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec1/1-0-sec-intro.html</loc>
-    <lastmod>2023-10-05T16:00:12.159Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.307Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec1/1-1-env-as-code.html</loc>
-    <lastmod>2023-10-05T16:00:12.187Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.327Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec1/1-2-proj-arch.html</loc>
-    <lastmod>2023-10-05T16:00:12.207Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.347Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec1/1-3-data-access.html</loc>
-    <lastmod>2023-10-05T16:00:12.259Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.387Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec1/1-4-monitor-log.html</loc>
-    <lastmod>2023-10-05T16:00:12.299Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.423Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec1/1-5-deployments.html</loc>
-    <lastmod>2023-10-05T16:00:12.323Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.439Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec1/1-6-docker.html</loc>
-    <lastmod>2023-10-05T16:00:12.343Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.455Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-0-sec-intro.html</loc>
-    <lastmod>2023-10-05T16:00:12.359Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.463Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-1-cloud.html</loc>
-    <lastmod>2023-10-05T16:00:12.387Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.495Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-2-cmd-line.html</loc>
-    <lastmod>2023-10-05T16:00:12.419Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.511Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-3-linux.html</loc>
-    <lastmod>2023-10-05T16:00:12.475Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.547Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-4-app-admin.html</loc>
-    <lastmod>2023-10-05T16:00:12.519Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.563Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-5-scale.html</loc>
-    <lastmod>2023-10-05T16:00:12.539Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.607Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-6-networking.html</loc>
-    <lastmod>2023-10-05T16:00:12.567Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.683Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-7-dns.html</loc>
-    <lastmod>2023-10-05T16:00:12.587Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.695Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec2/2-8-ssl.html</loc>
-    <lastmod>2023-10-05T16:00:12.599Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.707Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec3/3-0-sec-intro.html</loc>
-    <lastmod>2023-10-05T16:00:12.611Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.715Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec3/3-1-ent-networks.html</loc>
-    <lastmod>2023-10-05T16:00:12.639Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.727Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec3/3-2-auth.html</loc>
-    <lastmod>2023-10-05T16:00:12.655Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.743Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec3/3-3-ent-scale.html</loc>
-    <lastmod>2023-10-05T16:00:12.671Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.751Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/sec3/3-4-ent-pm.html</loc>
-    <lastmod>2023-10-05T16:00:12.679Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.763Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/append/auth.html</loc>
-    <lastmod>2023-10-05T16:00:12.703Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.775Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/append/lb.html</loc>
-    <lastmod>2023-10-05T16:00:12.711Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.795Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/append/lab-map.html</loc>
-    <lastmod>2023-10-05T16:00:12.723Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.803Z</lastmod>
   </url>
   <url>
     <loc>https://do4ds.com/chapters/append/cheatsheets.html</loc>
-    <lastmod>2023-10-05T16:00:12.767Z</lastmod>
+    <lastmod>2023-10-05T18:04:02.843Z</lastmod>
   </url>
 </urlset>