Working with Channels in .NET

Подписаться 291 тыс.

Просмотров 30 тыс.

50% 1

Channels enable a producer to safely pass data over to a consumer along with the appropriate notifications in both directions.
In this episode, Stephen Toub chats with Rich about the what, why and how of using the System.Threadding.Channels library. They walk us through a simple demo of using channels and also discuss the various strategies at our disposal.
[00:55] - What are channels used for?
[01:35] - Creating a basic channel implementation
[09:15] - Moving to System.Threadding.Channels
[11:34] - What are the benefits of using the System.Threadding.Channels?
[14:11] - What are some of the available back pressure strategies?
[20:58] - Working with varying number of producers or consumers
[21:54] - What are the merits of Channels compared to Pipelines?
[23:35] - Can channels be used out of process scenarios?
[24:30] - Can channels be used with pub/sub
[25:28] - What’s next for channels?
An introduction to System.Threading.Channels
devblogs.microsoft.com/dotnet...
System.Threading.Channels NuGet package
www.nuget.org/packages/System...
System.Threadding.Channels on GitHub
github.com/dotnet/runtime/tre...
#dotnet #channel #concurrency #runtime

Наука

Опубликовано:

3 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 43

@draganradovac8803 6 месяцев назад

Learning is always so easy with Stephen Toub

@dune102 4 года назад

Nice format, very informative. Thanks for showing the code, I was able to put it in Visual Studio and try it out. Great way to learn.

@sergeymikolaitis8205 3 года назад

Guys, thanks for this! Informative, useful, clear. I'm pumped for all of the performance improvements things.

@EzDoesntExist 4 года назад

Very informative way to demonstrate the idea.

@imensonspionrona2117 2 года назад

Good job men. This piece of infrastructure was desperately needed!

@krishnaraj8361 2 года назад

Nice, Thanks for the good session.

@dcuccia 4 года назад

Great discussion! Liked the comparisons to pipelines and pub/sub. Surprised, however, there was no comparison to all the Rx stuff.

@johnnm3207 4 года назад

Awesome, thanks I was reading about this last week

@CecilPhillip 4 года назад

Channels are amazing once you understand their use case

@ssoltani498 4 года назад

@@CecilPhillip is there any real world example of that?

@willinton06 4 года назад

S Soltani I can think of a couple hundred, basically any time you need to asynchronously listen and react to an API, I have my own implementation of this in basically every server I make, of this shows promise I might go back and refactor a little, although it would be an aesthetic decision, for this is wouldn’t make much of a difference to my implementation, I’ll de finely use channels in future projects tho

@5pirithief 4 года назад

@@ssoltani498 Channels can be used like Dataflow blocks. This tutorial gives you real-life scenarios: docs.microsoft.com/en-us/dotnet/standard/parallel-programming/dataflow-task-parallel-library Here is a nice article that explains the difference between Dataflow vs Channel: devblogs.microsoft.com/dotnet/an-introduction-to-system-threading-channels/ github.com/dotnet/runtime/issues/25439

@ivandrofly 19 дней назад

Thank you :)

@letgabeequaltrue9097 4 года назад

I never knew the lead singer to Metallica had a coding channel

@NavedRasul Год назад

Great (high quality) learning content guys! It helped me a lot. Hope it does others as well. 👍🏼🙂

@RasmusSchultz 4 года назад

What I don't feel you addressed was, what is this for? What are the concrete use-cases for this mechanism? Might be a topic for a follow-up episode.

@dandoescode 4 года назад

Aggreed. I thought a more concrete example is really needed to drive the point home. For example a couple of services responsible for certain tasks, and how this plays with DI. Obviously both services would need to be aware of exactly the same channel.

@ivandrofly 19 дней назад

10:19 - bound vs unbound writing 21:50 - comparison with Pipelines

@AdamsTaiwan 4 года назад

So I have c# like Notebook app and run workflows in the background. There are several ways of displaying information and would like to know what tech. would work best: Channel, Pipeline, other? 1. Showing progress (ok to lose frames of data) 2. Logging results to a file (frames of data cannot be missed) 3. Logging results to a view (frames of data cannot be missed) I tried using ShareMemory for the progress and reading just last value when possible, but takes a bit to setup.

@christopherhill9348 4 года назад

Great feature! I have code to refactor!

@MrRishabSharma 4 года назад

Good enough information to getting started but Is there a way i can connect two different services using a separate channel service and how can i migrate this in memory operation to a persistent data store for fault tolerant

@johnernest8109 4 года назад

Since Channel.CreateUnbounded has a set number and capacity, is this useful in a scenario like a database record for example say you store a serialized JSON per record in the filesystem and want to avoid race conditions in a high concurrency scenario where clients may be reading from the same table at the same time, but you don't want them to read a record that's in the middle of being written so you need to implement record locking, and there could be multiple records queued up to be written at a time from different clients?

@conaxlearn8566 3 года назад

10:54 You're not the only one. 😂😂😂

@yasser2768 3 года назад

You need to add read based on value condition

@DriRoPeloMundo 4 года назад

can do a real case for use it?

@jianglongdu946 4 года назад

channel like blockingCollection , so what is diff ?

@srivathsaharishvenk Год назад

Reactive extensions is much more powerful as it is much higher in abstraction, but this has better backpressure semantics, as this is a low-level construct