Concurrency is about handling multiple tasks at the same time. Its primary goal is correctness-not performance.  

Without proper coordination, concurrent systems become unpredictable.    
  
Concurrency enables programs to utilize multiple cores and scale, but it does not guarantee parallel execution.  

## Concurrency vs Parallelism  

Concurrency defines multiple tasks that can run independently.
The runtime schedules them, while parallelism determines whether they execute simultaneously on multiple cores.

## Learning Path 
1. Seeing Concurrency
2. Breaking Things 
3. Understanding Why
4. Controlling execution
5. Building async systems 
6. Ensuring correctness
7. Upgrading the execution model
8. Debugging real issues
9. Designing real systems  

&nbsp;  
Follow the weeks in order-the concepts build on each other.  
&nbsp;    
## Roadmap 
- [Week 0: Same Code, Different Output](./concurrency/week0)
- [Week 1: Race Conditions](./concurrency/week1)
- [Week 2: Memory Visibility](./concurrency/week2)
- [Week 3: Executors & Thread Pools](./concurrency/week3)
- [Week 4: ForkJoin & Parallelism](./concurrency/week4)
- [Week 5: CompletableFuture (Core)](./concurrency/week5)
- [Week 6: CompletableFuture (Advanced)](./concurrency/week6)
- [Week 7: Locks & Synchronization](./concurrency/week7)
- [Week 8: Concurrent Collections & Atomics](./concurrency/week8)
- [Week 9: Virtual Threads](./concurrency/week9)
- [Week 10: Debugging & Performance](./concurrency/week10)
- [Week 11: Real-World Concurrency Design](./concurrency/week11)
---



<p>Concurrency is about handling multiple tasks at the same time. Its primary goal is correctness-not performance.</p>
<p>Without proper coordination, concurrent systems become unpredictable.</p>
<p>Concurrency enables programs to utilize multiple cores and scale, but it does not guarantee parallel execution.</p>
<h2 id="concurrency-vs-parallelism">Concurrency vs Parallelism</h2>
<p>Concurrency defines multiple tasks that can run independently.
The runtime schedules them, while parallelism determines whether they execute simultaneously on multiple cores.</p>
<h2 id="learning-path">Learning Path</h2>
<ol>
<li>Seeing Concurrency</li>
<li>Breaking Things</li>
<li>Understanding Why</li>
<li>Controlling execution</li>
<li>Building async systems</li>
<li>Ensuring correctness</li>
<li>Upgrading the execution model</li>
<li>Debugging real issues</li>
<li>Designing real systems</li>
</ol>
<p> <br>
Follow the weeks in order-the concepts build on each other.<br>
 </p>
<h2 id="roadmap">Roadmap</h2>
<ul>
<li><a href="./concurrency/week0">Week 0: Same Code, Different Output</a></li>
<li><a href="./concurrency/week1">Week 1: Race Conditions</a></li>
<li><a href="./concurrency/week2">Week 2: Memory Visibility</a></li>
<li><a href="./concurrency/week3">Week 3: Executors &#x26; Thread Pools</a></li>
<li><a href="./concurrency/week4">Week 4: ForkJoin &#x26; Parallelism</a></li>
<li><a href="./concurrency/week5">Week 5: CompletableFuture (Core)</a></li>
<li><a href="./concurrency/week6">Week 6: CompletableFuture (Advanced)</a></li>
<li><a href="./concurrency/week7">Week 7: Locks &#x26; Synchronization</a></li>
<li><a href="./concurrency/week8">Week 8: Concurrent Collections &#x26; Atomics</a></li>
<li><a href="./concurrency/week9">Week 9: Virtual Threads</a></li>
<li><a href="./concurrency/week10">Week 10: Debugging &#x26; Performance</a></li>
<li><a href="./concurrency/week11">Week 11: Real-World Concurrency Design</a></li>
</ul>
<hr>