benn.substack.com/p/the-data-os/comment/2798462
Preview meta tags from the benn.substack.com website.
Linked Hostnames
3Thumbnail
Search Engine Appearance
Steve Touw on benn.substack
Great article! To me, SQL is the "common utility". dbt does "in batch" what Trino/Presto does "live". Trino/Presto is able to join across disparate databases, e.g. more than a switchboard (or at least the same level of switchboard as dbt). So either (or both) are viable and great options because they are both SQL-based abstractions. I also agree the formal definition of the mesh is very lacking on: "What happens on the other side of the mesh, or even what the mesh actually is, isn’t discussed"
Bing
Steve Touw on benn.substack
Great article! To me, SQL is the "common utility". dbt does "in batch" what Trino/Presto does "live". Trino/Presto is able to join across disparate databases, e.g. more than a switchboard (or at least the same level of switchboard as dbt). So either (or both) are viable and great options because they are both SQL-based abstractions. I also agree the formal definition of the mesh is very lacking on: "What happens on the other side of the mesh, or even what the mesh actually is, isn’t discussed"
DuckDuckGo
https://benn.substack.com/p/the-data-os/comment/2798462Steve Touw on benn.substack
Great article! To me, SQL is the "common utility". dbt does "in batch" what Trino/Presto does "live". Trino/Presto is able to join across disparate databases, e.g. more than a switchboard (or at least the same level of switchboard as dbt). So either (or both) are viable and great options because they are both SQL-based abstractions. I also agree the formal definition of the mesh is very lacking on: "What happens on the other side of the mesh, or even what the mesh actually is, isn’t discussed"
General Meta Tags
20- titleComments - The data OS - by Benn Stancil - benn.substack
- title
- title
- title
- title
Open Graph Meta Tags
7- og:urlhttps://benn.substack.com/p/the-data-os/comment/2798462
- og:imagehttps://substackcdn.com/image/fetch/$s_!Jlr7!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Fbenn.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-637874724%26version%3D9
- og:typearticle
- og:titleSteve Touw on benn.substack
- og:descriptionGreat article! To me, SQL is the "common utility". dbt does "in batch" what Trino/Presto does "live". Trino/Presto is able to join across disparate databases, e.g. more than a switchboard (or at least the same level of switchboard as dbt). So either (or both) are viable and great options because they are both SQL-based abstractions. I also agree the formal definition of the mesh is very lacking on: "What happens on the other side of the mesh, or even what the mesh actually is, isn’t discussed"
Twitter Meta Tags
8- twitter:imagehttps://substackcdn.com/image/fetch/$s_!Jlr7!,f_auto,q_auto:best,fl_progressive:steep/https%3A%2F%2Fbenn.substack.com%2Ftwitter%2Fsubscribe-card.jpg%3Fv%3D-637874724%26version%3D9
- twitter:cardsummary_large_image
- twitter:label1Likes
- twitter:data11
- twitter:label2Replies
Link Tags
21- alternate/feed
- apple-touch-iconhttps://substackcdn.com/icons/substack/apple-touch-icon.png
- canonicalhttps://benn.substack.com/p/the-data-os/comment/2798462
- iconhttps://substackcdn.com/icons/substack/icon.svg
- preconnecthttps://substackcdn.com
Links
19- https://benn.substack.com
- https://benn.substack.com/p/the-data-os/comment/2798462
- https://benn.substack.com/p/the-data-os/comment/2800784
- https://benn.substack.com/p/the-data-os/comment/2873474
- https://benn.substack.com/p/the-data-os/comment/2874745