great video . Thanks Saeed! The Background services in ASP NET Core always cause confusion between developers. In terms of Background Services, it will act in a blocking fashion until reaching the first async method ( that is why some say that it is best practice to do a "await Task.Yield()" at the first line of your background jobs
Greate! thanks Saeed. how if we have many DoNothing(). are we should put Yield as many method as we called? the second, how process long running sub method as background proses?
Glad you like the video, you can use Task.Yield as many as you can, no issue with that but better to use it when needed to avoid extra overhead for runtime. I didn't get the second question, can you explain more.
There's no guarantee that await returns the thread and runs on another. This code example is synchronous even tho it has multiple await keywords, thus code execution is continued using the same thread, until its blocked by that void method. If you want your program execution to be delayed - make it explicit, but inheriting from IHostedService interface instead of BackgroundService class.
But using IHostedService won't solve the problem, we need to make sure to not use sync method in async methods. And it can happend a lot when using nuget packages that don't support async like Kafka consumer method!
@@sa-es-ir It actually does solve it kind of. You might be doing database migrations, so it's fine to block startup. And sync methods are fine, as long as they are not I/O bound. Your whole workflow is synchronous here. Whole point of await keyword is make your operations non blocking for threads. Anyway, still a valid point. Thanks
You're right there is no synchronizationContext in the Asp.net core and the main thread is coming from my old habbits when was working with the winforms😁
why await ServiceMethod(or other await's for layers) not acting like Task.Yield? i dont really get it. I would expect it act like Task.Yield so other layers would run on another thread. But as you said its really running on same thread until db.
async methods starting 'synchronously' and it makes sense. Task is an object and one of those methods should create an actual Task to return and who did that in my example? Yes Task.Delay!
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
great video . Thanks Saeed!
The Background services in ASP NET Core always cause confusion between developers.
In terms of Background Services, it will act in a blocking fashion until reaching the first async method ( that is why some say that it is best practice to do a "await Task.Yield()" at the first line of your background jobs
Well said, happy you like the video
Very well spotted !
Glad you like it
Greate! thanks Saeed.
how if we have many DoNothing(). are we should put Yield as many method as we called?
the second, how process long running sub method as background proses?
Glad you like the video, you can use Task.Yield as many as you can, no issue with that but better to use it when needed to avoid extra overhead for runtime.
I didn't get the second question, can you explain more.
There's no guarantee that await returns the thread and runs on another.
This code example is synchronous even tho it has multiple await keywords, thus code execution is continued using the same thread, until its blocked by that void method.
If you want your program execution to be delayed - make it explicit, but inheriting from IHostedService interface instead of BackgroundService class.
But using IHostedService won't solve the problem, we need to make sure to not use sync method in async methods. And it can happend a lot when using nuget packages that don't support async like Kafka consumer method!
@@sa-es-ir It actually does solve it kind of. You might be doing database migrations, so it's fine to block startup.
And sync methods are fine, as long as they are not I/O bound. Your whole workflow is synchronous here. Whole point of await keyword is make your operations non blocking for threads.
Anyway, still a valid point. Thanks
@@Fikusiklol For migrations totally agree as they are critical for the application and db, thanks for sharing your insight
What do you mean by "main thread " ?ASP NET Core does not have main thread ( and synchronization context)
You're right there is no synchronizationContext in the Asp.net core and the main thread is coming from my old habbits when was working with the winforms😁
why await ServiceMethod(or other await's for layers) not acting like Task.Yield? i dont really get it. I would expect it act like Task.Yield so other layers would run on another thread. But as you said its really running on same thread until db.
async methods starting 'synchronously' and it makes sense.
Task is an object and one of those methods should create an actual Task to return and who did that in my example? Yes Task.Delay!