Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Topics

Loading

Aporeon

Technical interview practice, from one developer to another.

About Privacy Terms

.NET Concurrency & Parallelism

Parallel Workloads

CPU-bound work, controlled parallelism, safe aggregation, failure semantics, and throughput trade-offs.

12 drillsPractice one at a timeOrdered pathArchitecture scenarioComparison questionDebugging scenarioConcept question

Recommended start

CPU-bound API Work

Decide how to handle CPU-heavy work in an API without damaging request throughput or making the system unreliable.

Hard~12 minStep 1 of 12

Practice this drill Choose another

Search

12 of 12 shown

1CPU-bound API WorkRecommended startDecide how to handle CPU-heavy work in an API without damaging request throughput or making the system unreliable.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 2ForEachAsync vs WhenAllCompare Parallel.ForEachAsync and Task.WhenAll for processing collections with async work and controlled concurrency.Comparison questionMedium~7 min.NETASP.NET CoreC#Practice 3Channel<T>Use Channel<T> to coordinate producer/consumer background processing inside a .NET service while respecting backpressure and shutdown.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 4Background Job SafetyDesign background jobs that handle cancellation, retries, and duplicate execution without corrupting external state.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 5Limit External CallsDesign a bounded-concurrency approach for calling an external API safely from .NET code.Architecture scenarioMedium~10 min.NETASP.NET CoreC#Practice 6BackgroundService ShutdownExplain how a .NET BackgroundService should handle cancellation, in-flight work, and application shutdown.Debugging scenarioMedium~10 min.NETASP.NET CoreC#Practice 7PLINQ vs Parallel.ForEachChooses a parallel API based on whether the workload is a data query or an imperative loop and keeps CPU work pure, bounded, and measurable.Comparison questionMedium~7 min.NETC#Practice 8Degree of parallelismSets concurrency from the constrained resource and verifies throughput, latency, and downstream safety instead of maximizing active work.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 9DbContext and parallel workDiagnoses thread-unsafe scoped dependencies inside parallel execution and redesigns the data boundary without exhausting shared resources.Debugging scenarioHard~12 min.NETASP.NET CoreC#Practice 10Safe parallel aggregationUses reduction, thread-local state, atomic scalar updates, or indexed output instead of mutating a shared collection from parallel workers.Concept questionHard~9 min.NETC#Practice 11Parallel failure semanticsDefines what happens when several operations fail, cancellation arrives, or only part of a parallel batch completes, without orphaning work or hiding errors.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice 12Measure parallel speedupProves parallel speedup against a sequential baseline while accounting for overhead, saturation, tail latency, resource contention, and downstream impact.Architecture scenarioHard~12 min.NETASP.NET CoreC#Practice

Practice order

12 drillsOne at a time

1CPU-bound API WorkUp next / Hard / ~12 min
2ForEachAsync vs WhenAllMedium / ~7 min
3Channel<T>Hard / ~12 min
4Background Job SafetyHard / ~12 min
5Limit External CallsMedium / ~10 min
6BackgroundService ShutdownMedium / ~10 min
7PLINQ vs Parallel.ForEachMedium / ~7 min
8Degree of parallelismHard / ~12 min

+4 more drills in this section