87 lines
3.5 KiB
Markdown
87 lines
3.5 KiB
Markdown
---
|
||
date: '2022-11-20T11:35:46'
|
||
hypothesis-meta:
|
||
created: '2022-11-20T11:35:46.410564+00:00'
|
||
document:
|
||
title:
|
||
- 'Data Engineering in 2022: ELT tools'
|
||
flagged: false
|
||
group: __world__
|
||
hidden: false
|
||
id: eYCrpGjHEe2hEkur1Ic5ww
|
||
links:
|
||
html: https://hypothes.is/a/eYCrpGjHEe2hEkur1Ic5ww
|
||
incontext: https://hyp.is/eYCrpGjHEe2hEkur1Ic5ww/rmoff.net/2022/11/08/data-engineering-in-2022-elt-tools/
|
||
json: https://hypothes.is/api/annotations/eYCrpGjHEe2hEkur1Ic5ww
|
||
permissions:
|
||
admin:
|
||
- acct:ravenscroftj@hypothes.is
|
||
delete:
|
||
- acct:ravenscroftj@hypothes.is
|
||
read:
|
||
- group:__world__
|
||
update:
|
||
- acct:ravenscroftj@hypothes.is
|
||
tags:
|
||
- ELT
|
||
- data-engineering
|
||
target:
|
||
- selector:
|
||
- endContainer: /main[1]/article[1]/div[5]/div[1]/div[4]/p[1]
|
||
endOffset: 521
|
||
startContainer: /main[1]/article[1]/div[5]/div[1]/div[4]/p[1]
|
||
startOffset: 0
|
||
type: RangeSelector
|
||
- end: 4166
|
||
start: 3645
|
||
type: TextPositionSelector
|
||
- exact: "It took me a while to grok where dbt comes in the stack but now that\
|
||
\ I (think) I have it, it makes a lot of sense. I can also see why, with my\
|
||
\ background, I had trouble doing so. Just as Apache Kafka isn\u2019t easily\
|
||
\ explained as simply another database, another message queue, etc, dbt isn\u2019\
|
||
t just another Informatica, another Oracle Data Integrator. It\u2019s not\
|
||
\ about ETL or ELT - it\u2019s about T alone. With that understood, things\
|
||
\ slot into place. This isn\u2019t just my take on it either - dbt themselves\
|
||
\ call it out on their blog:"
|
||
prefix: "t could fail\u2026but not for now.\n\n\n"
|
||
suffix: '
|
||
|
||
|
||
|
||
|
||
|
||
dbt is the T in ELT
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
'
|
||
type: TextQuoteSelector
|
||
source: https://rmoff.net/2022/11/08/data-engineering-in-2022-elt-tools/
|
||
text: Also - just because their "pricing" page caught me off guard and their website
|
||
isn't that clear (until you click through to the technical docs) - I thought it's
|
||
worth calling out that DBT appears to be an open-core platform. They have a SaaS
|
||
offering and also an open source python command-line tool - it seems that these
|
||
articles are about the latter
|
||
updated: '2022-11-20T11:35:46.410564+00:00'
|
||
uri: https://rmoff.net/2022/11/08/data-engineering-in-2022-elt-tools/
|
||
user: acct:ravenscroftj@hypothes.is
|
||
user_info:
|
||
display_name: James Ravenscroft
|
||
in-reply-to: https://rmoff.net/2022/11/08/data-engineering-in-2022-elt-tools/
|
||
tags:
|
||
- ELT
|
||
- data-engineering
|
||
- hypothesis
|
||
type: reply
|
||
url: /replies/2022/11/20/1668944146
|
||
|
||
---
|
||
|
||
|
||
|
||
<blockquote>It took me a while to grok where dbt comes in the stack but now that I (think) I have it, it makes a lot of sense. I can also see why, with my background, I had trouble doing so. Just as Apache Kafka isn’t easily explained as simply another database, another message queue, etc, dbt isn’t just another Informatica, another Oracle Data Integrator. It’s not about ETL or ELT - it’s about T alone. With that understood, things slot into place. This isn’t just my take on it either - dbt themselves call it out on their blog:</blockquote>Also - just because their "pricing" page caught me off guard and their website isn't that clear (until you click through to the technical docs) - I thought it's worth calling out that DBT appears to be an open-core platform. They have a SaaS offering and also an open source python command-line tool - it seems that these articles are about the latter |