iOS Dev 15: Concurrency Explained with Diagrams | Swift 5, XCode 11

Today we learn about Concurrency and how we can improve our app's performance by applying it.

We learn the difference between Synchronous and Asynchronous programming and also identify scenarios where each of them can be used.

Next, we talk about the Main Queue, the dangers of blocking it, and how to create and manage concurrent queues using the Grand Central Dispatch (GCD).

Afterwards, we look into DispatchGroups and how we can use it to wait for the completion of all queues before executing an action.

Finally, we talk about the Quality of Service (QOS) outlining the various priority levels and when they might be used.

Say Hi on Social Media:

Additional Resources:

[deedan]

Now I understand concurrency better
Thank you, Emmanuel

[roh]

emmanuel, i became your fan from india. binge watching your series and learning alot.. Thank you, sir.

[kellyxiao]

really love your video and thanks for sharing your knowledge

[bravo]

I love your contents
You deserve more views!!

[kelvinfok]

how do we make a distinction between serial/concurrent vs synchronous/asynchronous? you described synchronous as serial, but I thought the definition was about blocking the thread.

[adewaleajayi]

Concurrency in its best form explained!!! You are awesome bro!!

[prashansamarathunge]

Your videos are Awesome Man. This is very useful... ♥

[kalidass]

Hai, your explanation is very neat and understandable. Thank you so much!.Can you please make a brief video with an UI example of Serial vs Conceurrent quese?

[KaizenM]

Great vid! What is the difference between DispatchQueue(label:).async and DispatchQueue.main.async?

[olajideosho]

A Comprehensive Guide to iOS development for those who have knowledge of Swift Programming Language as stated by the author. Thanks for broadening my understanding on DispatchGroups.
I perceive that your very busy, but please whenever you have the chance, I would really appreciate a video that explains concepts around "DispatchWorkItem".
Once again Thanks.