DiscoverData Engineering Concepts
Data Engineering Concepts
Claim Ownership

Data Engineering Concepts

Author: Dmitrii Polovinkin

Subscribed: 1Played: 9
Share

Description

Welcome to the first purely educational podcast about Data Engineering in English, I'm your host Dmitrii Polovinkin! This is a podcast about tools, technologies, and ideas that we data engineers work with every day. In relatively short episodes I break down one topic at a time - describing how modern data stack works, giving you explanations based on the real-world context and lessons from my 7+ years of working in as a data engineer in the variety of fields and projects. Subscribe to start learning and become a better data engineer! :)
9 Episodes
Reverse
What happens when multiple transactions hit the same data at the same time? In this episode of Data Engineering Concepts, we dive into transaction isolation levels — a classic interview topic and a must-know for anyone working with transactional systems. We start with the anomalies that isolation levels are designed to prevent: dirty writesdirty readslost updatesnon-repeatable readsread and write skewsand phantom reads.Then we walk up the "ladder" of the four main isolation levels: Read UncommittedRead CommittedRepeatable ReadAnd Serializableand look at how each one removes more anomalies at the cost of performance. Along the way, we touch on MVCC snapshots in PostgreSQL, why isolation levels can behave differently across database systems (hello, DB2's cursor stability), and how Serializable Snapshot Isolation can even roll back your queries.By the end, you'll have a solid foundation for understanding how parallel transactions interact — and how to keep your data consistent.🎙️ Data Engineering Concepts — making complex data engineering topics easier to understand, one episode at a time.Podcast website: 🌐 ⁠⁠⁠⁠https://deconcepts.com⁠⁠⁠⁠Add me on LinkedIn: ⁠⁠⁠https://www.linkedin.com/in/dpolovinkin⁠⁠
How does database replication work, and why is it so important for modern data systems?In this episode of Data Engineering Concepts, we explore database replication — one of the fundamental techniques for improving high availability, scaling read workloads, and building resilient data architectures.We'll break down the main replication approaches, explain how they differ, and discuss the trade-offs you should understand as a data engineer.In this episode:What database replication is and why we use itPhysical vs. logical replication and Change Data Capture (CDC)Block-level and application-level replicationSynchronous vs. asynchronous replicationSingle-leader, multi-leader, and leaderless architecturesReplication lag, consistency, and potential data lossRecovery Time Objective (RTO) and Recovery Point Objective (RPO)Why replication doesn't replace proper backupsWhether you're preparing for a data engineering interview or looking to strengthen your understanding of database architecture, this episode will help you build a clearer picture of how replication works.If you find this episode useful, consider following the podcast and leaving a rating or review!🎙️ Data Engineering Concepts — making complex data engineering topics easier to understand, one episode at a time.Podcast website: 🌐 ⁠⁠⁠https://deconcepts.com⁠⁠⁠Add me on LinkedIn: ⁠⁠https://www.linkedin.com/in/dpolovinkin⁠⁠
What is database normalization, and why does it matter?In this episode of Data Engineering Concepts, we explore the fundamentals of database normalization, from understanding data redundancy and modification anomalies to breaking down normal forms, including 1NF, 2NF, 3NF, BCNF, 4NF, and 5NF.We'll also discuss candidate keys, functional dependencies, and the practical trade-offs between normalized and denormalized data.Is normalization always the right choice? And why might denormalization actually be preferable for analytical workloads?Whether you're preparing for a data engineering interview or simply looking to strengthen your database fundamentals, this episode will help you better understand when and why normalization matters.If you find this episode useful, consider following the podcast and leaving a rating or review!🎙️ Data Engineering Concepts — making complex data engineering topics easier to understand, one episode at a time.Podcast website: 🌐 ⁠⁠⁠https://deconcepts.com⁠⁠⁠Add me on LinkedIn: ⁠⁠https://www.linkedin.com/in/dpolovinkin⁠⁠
CAP Theorem Explained

CAP Theorem Explained

2026-10-1510:37

What is the CAP theorem, and why does it matter in distributed systems?In this episode, we explore the CAP theorem and its three fundamental properties: Consistency, Availability, and Partition Tolerance. We'll discuss what these properties mean, why distributed systems have to make trade-offs when network failures occur, and how AP and CP systems differ.We'll also look at the limitations of the CAP theorem and introduce PACELC, a more modern approach that considers the trade-offs between latency and consistency even when everything is working normally.If you find this episode useful, consider following the podcast and leaving a rating or review!🎙️ Data Engineering Concepts — making complex data engineering topics easier to understand, one episode at a time.Podcast website: 🌐 ⁠⁠⁠https://deconcepts.com⁠⁠⁠Add me on LinkedIn: ⁠⁠https://www.linkedin.com/in/dpolovinkin⁠⁠
What is Medallion Architecture, and why is it commonly used in modern data platforms?In this episode, we explore the fundamentals of Medallion Architecture and its three core layers: Bronze, Silver, and Gold. We'll discuss the purpose of each layer, how data moves from raw sources to business-ready datasets, and how this approach relates to traditional data warehouse architectures.We'll also touch on ELT processing and walk through a practical example to see how it all works.If you find this episode useful, consider following the podcast and leaving a rating or review!🎙️ Data Engineering Concepts — making complex data engineering topics easier to understand, one episode at a time.Podcast website: 🌐 ⁠⁠https://deconcepts.com⁠⁠Add me on LinkedIn: ⁠https://www.linkedin.com/in/dpolovinkin⁠
loading
Comments