Pratique du Shadowing: Database vs Data Warehouse vs Data Lake | Explaining the Differences - Apprendre l'anglais à l'oral avec la vidéo

We live in a world that runs on data.

It's how Amazon and Netflix know which movies and products to recommend, how Starbucks manages a global supply chain,

and how Uber connects drivers with passengers in real time.

But the thing is, data skills aren't just for tech companies or professional analysts anymore.

Everyone works with data to some degree, and everyone can benefit from data literacy skills.

In this video, we're covering an important topic that will help you take your data literacy to the next level.

Alright, so accessing data is one thing, but organizing and storing it is a completely different beast.

So at a high level, some of the most common storage modes that you're likely to encounter include flat files, databases, data warehouses, and data lakes.

Now, there are other, less common storage methods and hybrid variations of these as well, but our goal here is really just to paint some broad strokes

and help you understand the key similarities and differences between them.

Now, the simplest method of data storage is a flat file,

which is typically a static tabular data extract saved either to a local drive or cloud storage like Google Drive or OneDrive.

And this is very common for one off projects or quick ad hoc analyses that don't require multiple data sources, ongoing maintenance or complex data models.

The most common types of flat files you'll see are CSVs and Excel workbooks.

Now, a database is a collection of related tables stored in a database management system, or DBMS.

Databases are typically used for recording and collecting data tied to a single application or business process,

like capturing transactional records or real-time website activity.

And they're usually optimized for online transactional processing,

known as OLTP, meaning that they're built to receive and store data as efficiently as possible, but aren't really ideal for querying or analysis.

Common database options include MySQL, Amazon RDS, Microsoft Access or SQL Server, and many, many more.

A data warehouse, on the other hand, is a database

or a collection of data sourced from multiple databases that's typically structured to support specific analytics needs

and is optimized for online analytical processing, or OLAP.

That basically just means it's built in a way

that makes it very easy and very fast for users to access the data they need for analytical purposes.

examples of data warehouse tools include Amazon Redshift, Google BigQuery, Snowflake, Teradata, and others.

And finally we have data lakes which are essentially a repository of both structured

and unstructured data sources often stored in their raw unprocessed state.

So we're talking about everything from CSV files to MP4s, PDFs, text documents, and so on.

Instead of getting Being cleaned and prepped on the way in, data is typically extracted from the lake and transformed for specific purposes,

often relating to machine learning or AI.

Some examples of data lakes include Amazon S3, Azure Data Lake, Google Cloud, and more.

Now, if you're feeling a little overwhelmed about what this all means, no need to worry.

I've worked in data analytics and business intelligence for over 15 years, and I still get confused by this stuff.

The good news is that unless you plan to become a data engineer, it's extremely unlikely that you would be the one building or configuring databases or warehouses.

In fact, in most cases, data engineers or architects are the ones primarily responsible for standing up these systems

and building the pipelines and automations that help the data flow from one place to another.

If you enjoyed this content and want to see more, we've got a brand new Data Literacy Foundations course, and it's entirely free.

You can check it out at mavenanalytics.io.

So whether you're an individual looking to build confidence, a leader seeking to empower and upskill your team, or a data professional just trying to to stay ahead of the curve,

this is the course for you.

We've got a lot to cover, so let's dive in.

📺 Même chaîne

How to Think Like a Data Analyst | Step-by-Step Guide

University StudentsBusiness English+1

✨ Vidéo recommandée

220 phrases

Qu'est-ce que la technique du Shadowing ?

Le Shadowing est une technique d'apprentissage des langues fondée sur la science, développée à l'origine pour la formation des interprètes professionnels. Le principe est simple mais puissant : vous écoutez de l'anglais natif et le répétez immédiatement à voix haute — comme une ombre suivant le locuteur avec un décalage de 1 à 2 secondes. Les recherches montrent une amélioration significative de la précision de la prononciation, de l'intonation, du rythme, des liaisons, de la compréhension orale et de la fluidité.

Technique du shadowing : lire le guide complet étape par étape →

Pratique du Shadowing: Database vs Data Warehouse vs Data Lake | Explaining the Differences - Apprendre l'anglais à l'oral avec la vidéo

How to Think Like a Data Analyst | Step-by-Step Guide

How Modern Data Teams Work (Engineer, Analyst, Scientist, Architect, ML)

The Secret Sauce Behind NoSQL: LSM Tree

What is Master Data Management? MDM Explained for Beginners

What is a Server? Servers vs Desktops Explained

Amazon Athena explained in 120 seconds💡

Microservices with Databases can be challenging...

Introduction to HPLC - Lecture 1: HPLC Basics

Database vs Data Warehouse vs Data Lake | What is the Difference?

Claude Cowork Tutorial: Build Monthly Reports in Minutes

User Flow vs Task Flow in UX Design

What is Event Driven Architecture (EDA)?

World’s most advanced robotic warehouse (AI automation)

À propos de cette leçon

Qu'est-ce que la technique du Shadowing ?