쉐도잉 연습: What Is a Data Mesh? Databricks Unity Catalog Explained - 영상으로 영어 말하기 배우기

연습 모드 선택

각 모드는 전체 화면 연습실로 열립니다.

147 문장
문장이 너무 짧거나 길면 Edit를 눌러 조정하세요.
1
to make everything is clean
2
and it's clear who is offering what what we're gonna do
3
we are back yeah to the hub a little bit
4
but this time this hub is marketplace what do we have
5
in the marketplace is the following everyone gonna announce their products into central place say hey
6
i offer the sales data hey i offers the hr data hey
7
i offer the finance data maybe not not arrows sorry for
8
that yeah arrows okay
9
so the dotted arrow means not the data gonna move to central place
10
this is very important to understand the data gonna stay at their places yeah
11
so it stays at domain a stays at domain b it stays at domain d
12
and so on it's just we're gonna make one gigantic catalog about the data into central place
13
so it is a marketplace where everyone announcing their data
14
i have the sales i have five tables i have 10 tables
15
so it's like bizarre it is very very cool
16
because the data analyst they just go to the marketplace
17
and read it
18
and they can understand okay the whole company how many data
19
do we have how many tables how many domains how the size without doing
20
this journey by visiting each of those domains without running around in circles to find the data
21
they're to go to one place and my friends she gonna find the data fast
22
and she gonna understand aha in order to make my reports
23
i need the sales data i need this i need
24
that i need from this and i'm gonna be able to work
25
but this is not only for the analyst as well for
26
the ai engineer for any new projects have been in the company
27
we know where the data is um
28
this is why we're gonna need a central market central place by the way
29
this is not anymore federated i just introduced you to the data mesh
30
it's not anymore federated things are going to the middle
31
so data mesh is no more central team doing the whole thing yeah this is very clear
32
because we have federated we split the data by domains each domain
33
they're gonna do the whole thing alone we're gonna have data as a product
34
that means we're gonna have documentations i'm gonna explain more what is data as a product
35
because it's way more than that
36
but we're gonna have each domain
37
they're gonna make a catalog about their data into central place the marketplace
38
they're gonna document it they have a product owners
39
and everything is like systemized and documented with high quality
40
and all those stuff so the data mesh concept says again physically each domain gonna have
41
that data they're gonna own the data at their own place
42
they never go to the central place they never go to the hub
43
they never go to the central lake house they're gonna stay at
44
that department at the domain physically gonna stay at the domains
45
but we're gonna make a virtual place where the whole metadata of the whole company gonna be described
46
so that if auditor comes they can read the marketplace
47
if a new developers comes to the company they're gonna go to the marketplace
48
if any news gate new data use case happen to the company we start from the marketplace
49
and understand it this picture it is not only the companies
50
that understood it who understood this as well it's always the data Databricks.
51
They are very, very up to date with all pains of companies.
52
This is amazing, really.
53
I'm not trying here to sell anything, okay?
54
I'm not sponsored or something from Databricks.
55
I'm just trying to say here.
56
Databricks came and understood, oh, companies are moving to this.
57
How about I'm gonna offer something similar to this?
58
I would like, like, because Databricks stopped us here.
59
Let me just take the icon.
60
Now, I'm breaking a little bit the vendor, okay?
61
But it is not that important.
62
Now, Databricks at the start stopped at here and said, hey, you can make
63
Spark, you can make lake houses.
64
It's the best thing.
65
And they start selling this like crazy.
66
But they saw this is happening.
67
Companies are making multiple lake houses left and right, and they're going to need something called marketplace.
68
And now if you are learning Databricks, you're going to understand the origins of the Unity Catalog.
69
Unity Catalog is made for this is made in order to
70
make data mesh concepts in order to make domain -driven architectures
71
this is what we call domain you're gonna hear a lot
72
if you go as an architect people are making domain oriented
73
or domain driven architecture
74
and this is exactly what we mean at the data world we say data mesh
75
and now the vendor databricks join this picture
76
this is exactly what they are trying to sell for the companies yeah i have some doubts about it
77
but it's working
78
but not for big companies yeah let me just explain where that's why two years ago yeah
79
i was making my projects
80
and then suddenly i've seen something called catalog yeah the catalog yeah the unity catalog
81
they introduced the unity catalog who knows the unity catalog data bricks had something similar like a marketplace
82
but it was not a marketplace
83
it was just a database catalog for your project just only for you for your project okay
84
and they called it the hive metastore it's legacy name you will not find it
85
but i'm just telling you the story about it they have like some kind
86
it looks like a database okay you are you are you are looking at the unit catalog
87
but it was only for you for your projects and They switch the whole thing to a marketplace.
88
So you see here, it's called my organization.
89
Well, maybe in big companies, it's going to be like the company's name.
90
And you will be able to browse not only your projects, but you're going to find as well all the catalogs of the whole company.
91
Now, I cannot show you the example because I have here only one example.
92
So imagine here, I'm going to see inside my organization, maybe 30 catalogs, the sales, after sales, the manufacturing and all those stuff so
93
that means they made this local catalog
94
that is available only for a project they made it only visible for the whole company
95
and this is what suddenly i was like working towards
96
and this happens to my project i was working at my project
97
and i saw only one catalog this is my catalog
98
and i'm doing the server bronze gold and i'm building the warehouse
99
and then in the next day i was not following the news i opened my catalog
100
and i saw 200 catalogs that's all because suddenly i'm able to see the whole company catalog.
101
They turned each local instance or each local project into like a global catalog that is available for everyone.
102
So everyone was able to see my projects and I am able to see everyone else's projects.
103
So that means if you are working in Databricks, this is the Unity catalog, my friends.
104
And with that, we just, I don't know, I think they did cost them a lot of work they just turned the local catalogs
105
that each project have into a global one
106
and they solved this issue with the data mesh
107
and that's exactly why we have now something called unity catalog
108
this is exactly the reason behind it they want everyone to be able to access everyone
109
or let's say everything should be visible for everyone else this is still issue the thing is the vendor, they are trying to, yeah,
110
to sell us this idea, which is amazing, I think.
111
But this is going to work, yeah, I'm going to say only if everyone is working in Databricks, right?
112
So if everyone is in Databricks, this is going to work because they're going to share their stuff to the middle, right?
113
Now, if a company gets, I don't know, sophisticated and they do things outside of catalog,
114
this is going to be challenging to make the Unity Catalog as a central place.
115
They try it's like there's some work around and stuff
116
but they it could work of course but
117
if the company have like on -prem solutions
118
if one domain is not working at all in the cloud
119
if other is using i don't know yeah azure we have azure stuff fabric
120
if the company is not clean about that platform strategy
121
and they allow multiple platforms then sadly this will not work that's why in some companies,
122
if they are big enough to say Databricks is not enough for them, they have to make their own catalog.
123
Like at the end, I'm going to show you a few examples.
124
I have made some with Claude.
125
I'm just prepared a few visuals for you.
126
Yeah, I don't have your catalog icon.
127
Let's bring this here.
128
So the company should then develop their own marketplace for this.
129
So my friends, this is very cool to understand what is a data mesh
130
and how our data is turning into something called products
131
so it is not anymore this picture where you have central data engineers just prepare the data
132
and give it the world is getting bigger
133
we are getting a lot of new things
134
we are focusing on only on domains we have yeah the product owners
135
we have a marketplace for data yeah
136
we are transitioning to this domain driven architecture
137
i'm really happy with this yeah it's like one of the best i'm gonna say
138
so far best practices on how to do it i love
139
this idea to have the metadata data into stored into one place
140
and as well to have the domains spread
141
it around don't store anything centrally for big companies it will not work
142
and yeah those discussions again happens at the elite level of the architect the principal architects
143
and let's say the big managers the data officers and stuff like
144
that so it's not something that we decide at our level level
145
but if you hear about it if you join a company
146
or something that they are doing domain you should know about the structure
147
and it is relevant for you as a data analyst and stuff like that.

앱 다운로드

유창하게 말하는 데 필요한 모든 것

AI 발음 평가문장마다 점수 확인
IPA 발음 연습모든 소리 마스터
단어 학습나만의 단어장 만들기
단어 게임놀면서 외우기

같은 채널

FOR YOU

추천 영상

이 레슨의 어휘와 말하기 포인트

이 말하기 레슨은 영상 “What Is a Data Mesh? Databricks Unity Catalog Explained”을(를) 바탕으로 합니다. 가장 자주 반복되는 단어는 다음과 같습니다: catalog, domain, marketplace, project, databricks. 이 영상에는 섀도잉할 문장 147개와 단어 1755개가 있습니다. 말하는 구간의 길이는 9:10입니다. 화자는 분당 약 191단어로 빠르게 말하므로 연음과 약하게 발음되는 소리가 많습니다. 단어의 85%가 영어에서 가장 많이 쓰이는 3,000단어에 속합니다. 나머지는 연습 전에 미리 확인해 두세요.

이 영상의 핵심 어휘

영상에 나오는 익혀 둘 만한 단어 15개를 발음, 뜻과 함께 정리했습니다.

단어발음뜻
catalogue 명사/ˈkæt.əˌlɔɡ/목록, 카탈로그
unity 명사/ˈjunɪti/단결, 단일
mesh 명사/mɛʃ/그물
architecture 명사/ˈɑː.kɪˌtɛk.t͡ʃə/건축, 건축학
arrow 명사/ˈæɹəʊ/화살
architect 명사/ˈɑɹ.kɪˌtɛkt/설계자, 계획자
vendor 명사/ˈvɛn.dɚ/판매인, 판매자
visible 형용사/ˈvɪzɪb(ə)l/보이는
introduce 동사/ˌɪntɹəˈdus/소개(紹介)하다
database 명사/ˈdeɪtəˌbeɪs/데이터베이스
announce 동사/əˈnaʊn(t)s/발표(發表)하다, 공포(公布)하다
icon 명사/ˈaɪ.kɑn/이콘, 성상
gate 명사/ˈɡeɪ̯t/문, 대문
cloud 명사/ˈklaʊ̯d/구름
server 명사/ˈsɝvɚ/서버, 봉사기

따라 말해 볼 만한 문장

영상에 나오는 짧고 완결된 문장으로, 일상 대화에서 그대로 쓸 수 있습니다:

  • I'm not trying here to sell anything, okay?
  • I'm just trying to say here.
  • How about I'm gonna offer something similar to this?
  • I'm just prepared a few visuals for you.

이 영상의 문법

화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.

문형영상 속 표현
현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때have been · have federated · i've seen
수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점be described · is made

주의할 발음

화자는 gonna, I'm, they're 같은 축약형과 약화된 형태를 68번 사용합니다. 들리는 대로 짧게 발음하세요.

  • “sh”와 “zh” 소리: mesh /mɛʃ/, transition /tɹænˈzɪʃ.ən/, documentation /ˌdɑkjəmɛnˈteɪʃən/, azure /ˈæʒɚ/
  • 긴 단어 — 강세 위치에 주의: architecture /ˈɑː.kɪˌtɛk.t͡ʃə/, developer /dɪˈvɛləpɚ/, documentation /ˌdɑkjəmɛnˈteɪʃən/, metadata /ˈmɛt.əˌdeɪ.tə/

한국어 화자가 어려워하는 소리:

  • /f/ — ㅍ(/p/)으로 바꾸지 말고 윗니를 아랫입술에 대기: physically /ˈfɪz.ɪ.kli/, fabric /ˈfæb.ɹɪk/, federate /ˈfɛdəɹeɪt/
  • /v/ — ㅂ(/b/)과 구별하기: vendor /ˈvɛn.dɚ/, visible /ˈvɪzɪb(ə)l/, server /ˈsɝvɚ/, solve /sɒlv/, virtual /ˈvɜɹt͡ʃuəl/
  • /z/ — ㅈ이 아니라 성대를 울리는 /s/: visible /ˈvɪzɪb(ə)l/, physically /ˈfɪz.ɪ.kli/, transition /tɹænˈzɪʃ.ən/, bronze /bɹɑnz/, bizarre /bɪˈzɑː(ɹ)/

이 영상으로 연습하는 방법

  1. 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
  2. 0.75배속으로 한 문장씩 섀도잉을 시작하고, 익숙해지면 보통 속도로 돌아갑니다.
  3. 자신의 목소리를 녹음해 원본과 비교하고, catalogue, unity, mesh 같은 단어에 특히 주의합니다.

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

섀도잉 방법: 단계별 전체 가이드 읽기 →