If you’re just starting to learn about operating system concepts and stumbled on the popular Deadlock educational series, your first question is probably how many episodes of deadlock are available to stream. The series has built a cult following among computer science students, junior devs, and system admins for its no-nonsense, easy to follow explanations of one of the most confusing OS topics out there. I’ve worked through the entire series twice now, once when I was studying for my OS certification and again last year when I was training new hires on system optimization, so I’ve got all the details you need to plan your viewing schedule.
How Many Episodes of Deadlock Are There, Exactly?
As of the latest content update, there are 37 official core episodes of the Deadlock series, plus 9 bonus Q&A episodes that drop quarterly for registered members of the creator’s learning platform. The core episodes are split into 4 seasons that align with the standard OS curriculum taught in most undergraduate computer science programs, so you can follow along even if you’re taking a related class at the same time.
You might see some older sources online claim there are only 28 episodes, but that count is from before the 4th season launched in late 2023. The creator also removed 2 low-performing early episodes in 2022 that covered outdated mainframe deadlock scenarios that don’t apply to modern cloud systems, so that older count is no longer accurate. If you’re accessing the series through official channels, you’ll see the full 37 core episodes sorted by season automatically.
It’s worth noting that the bonus Q&A episodes don’t count toward the official core count, but they’re incredibly useful if you’re stuck on a specific concept or want to see real-world troubleshooting examples. Most of these bonus episodes run 15 to 20 minutes, compared to the 30 to 40 minute runtime of core episodes, so they’re easy to fit in between longer study sessions.
What Each Deadlock Episode Covers
The series is structured to build your knowledge incrementally, so you won’t jump into complex detection algorithms before you understand the basic four conditions required for a deadlock to occur. The first 12 episodes (Season 1) focus entirely on foundational concepts, with real-world examples from retail point-of-sale systems, cloud server clusters, and even everyday scenarios like traffic jams to make abstract ideas feel tangible.
Season 2 has 10 episodes that dive deep into deadlock detection and recovery techniques, with step-by-step demos of popular detection tools used by DevOps teams at major tech companies. You’ll get to follow along as the creator walks through real outage reports from well-known service disruptions caused by unaddressed deadlocks, and walks through exactly how the engineering teams resolved them.
Season 3’s 8 episodes cover deadlock prevention techniques that you can implement immediately in your own code or server configurations. Each episode ends with a short quiz and hands-on exercise that lets you test what you learned, so you don’t just memorize concepts you can actually apply them. I found these exercises especially helpful when I was studying for my certification, as they let me practice identifying potential deadlock risks before they caused real issues.
The 7 episodes in Season 4, the most recent release, focus on deadlock in databases, which is a huge pain point for backend developers and database administrators. These episodes cover everything from transaction deadlocks in SQL databases to distributed deadlocks in NoSQL systems used for big data processing. A lot of viewers say this is the most useful season for working professionals, since database deadlocks are one of the most common causes of unexpected application slowdowns and outages.
How to Get the Most Out of the Deadlock Series
After working through the series twice and recommending it to dozens of students and new hires, I’ve got a few simple tips that will help you retain more information and avoid wasting time on content that’s not relevant to your goals. You don’t have to watch every episode in order if you already have some background in operating system concepts, but I do recommend watching the first 3 foundational episodes no matter your skill level to make sure you’re aligned with the creator’s framing of key concepts.
Here are my top tips for getting the best results from the series:
- Pause after each core episode to complete the linked hands-on practice exercises before moving on to the next topic. Most people forget 60% of new technical information within 24 hours if they don’t apply it, so this small step will double how much you retain.
- If you’re a working developer focused only on database issues, you can skip the Season 2 episodes focused on operating system level recovery and jump straight to Season 4 after finishing the first 3 foundational episodes.
- Set aside 90 minutes a week to watch 2 core episodes plus one bonus Q&A episode to build consistent progress without burning out. Most viewers finish the entire core series in 5 weeks with this schedule.
One mistake I see a lot of new viewers make is binging 5 or 6 episodes in a single sitting, then forgetting most of what they learned a week later. Deadlock concepts build on each other, so it’s much better to take your time and make sure you fully understand one topic before moving to the next. If you get stuck on a specific episode, check the comment section or the corresponding bonus Q&A episode, as 90% of common questions are already answered there.
You don’t need any special tools to follow along with the exercises, either. All the demos use free, open source software that runs on Windows, Mac, and Linux, so you won’t have to pay for any extra tools to complete the practice tasks.
Common Questions New Deadlock Viewers Ask
I get a lot of questions about the series from people who are just starting their OS learning journey, so I’ve rounded up the most common ones to save you time searching for answers. The first question I get almost every week is whether the series is worth watching if you don’t have a computer science degree. The short answer is yes, the creator explains every concept from the ground up, so you don’t need any prior technical background to follow along.
Another common question is whether the bonus episodes are worth paying for the premium membership. If you’re just learning for fun or to pass a single college class, you probably don’t need the bonus content. But if you’re planning to work in DevOps, backend development, or database administration, the bonus Q&A episodes include real case studies from working engineers that you won’t find in any textbook, so the membership fee is well worth the cost.
Some viewers also ask if there are plans for more episodes in the future. The creator announced earlier this year that they’re working on a 5th season focused on deadlocks in distributed cloud systems, which is expected to have 8 new core episodes launching next year. They also release a new bonus Q&A episode every 3 months, so the total content count will keep growing over time.
The last common question I get is whether the series is better than free deadlock tutorials on other platforms. In my experience, the Deadlock series is far more structured and practical than most free content, which usually only covers basic definitions without any real-world application. That said, if you’re on a tight budget, you can get a lot of value from the first 12 episodes that are available for free on public platforms, even if you don’t pay for the full series.
Whether you’re studying for a certification, prepping for a job interview, or just trying to fix deadlock issues in your own application, knowing how many episodes of deadlock are available helps you plan your learning schedule properly. The 37 core episodes cover every deadlock-related topic you could possibly need to know, and the incremental structure makes it easy to build your skills without feeling overwhelmed. Take your time working through the content, do the practice exercises, and you’ll be able to identify and resolve deadlocks with confidence in no time.