Getting Started with Python 3 Concurrency

What This Course Covers

You’ll start with threading fundamentals and the Global Interpreter Lock (GIL), then move into multiprocessing for true parallelism and async/await for I/O-bound operations. Tim Ojo walks through real scenarios: handling multiple database connections, managing API requests, and avoiding race conditions—the exact problems you’ll face in production systems.

The course emphasises choosing the right concurrency model for your use case rather than treating them as interchangeable. You’ll work through Pluralsight’s hands-on labs and sandboxes, so you’re not just watching—you’re writing concurrent code and seeing it fail and succeed in real time.

Who Is This Course For?

Ideal for:

• Backend engineers scaling Python services: You’re hitting performance bottlenecks with synchronous I/O and need to understand threading vs async without a 40-hour deep dive.
• DevOps and infrastructure developers: You’re automating deployments and managing concurrent tasks; this course clarifies when to use threading, multiprocessing, or async in your scripts.
• Mid-level Python developers expanding their toolkit: You’ve mastered the basics and now need concurrency patterns to handle real-world workloads and interview questions.

May not suit:

• Absolute Python beginners: You’ll need solid grasp of functions, decorators, and exception handling first; this assumes you’re comfortable with core Python syntax.
• Data scientists focused on pandas and ML: Concurrency isn’t your bottleneck; parallelisation libraries like Dask or Ray are more relevant to your workflow.

Frequently Asked Questions

How long does Getting Started with Python 3 Concurrency take?

2 hours 38 minutes of video content. Plan 3–4 hours total if you’re working through the hands-on labs and experimenting with code.

Will this course teach me async/await?

Yes. You’ll cover async/await syntax, event loops, and when to use it for I/O-bound operations. It’s one of three concurrency models covered alongside threading and multiprocessing.

Do I need to know about the GIL?

The course explains the Global Interpreter Lock and why it matters for threading. Understanding the GIL is crucial for choosing between threading and multiprocessing—Tim covers this clearly.

Can I access hands-on labs?

Yes. Pluralsight includes interactive labs and sandboxes where you write and test concurrent code directly in the browser, not just watch demonstrations.