tag:blogger.com,1999:blog-4063545436138319205.post4582495264437642076..comments2024-03-28T20:55:32.820-07:00Comments on Tom DuPont .NET: .NET Asynchronous Parallel Batch ProcessorTom DuPonthttp://www.blogger.com/profile/08233783264428691459noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4063545436138319205.post-19558457596567796782016-10-02T09:19:04.367-07:002016-10-02T09:19:04.367-07:00Thanks for bringing this up! I have used dataflow ...Thanks for bringing this up! I have used dataflow blocks form the TPL in the past to solve these sorts of problems, but I created this because I just wanted something small and lightweight. If you are doing anything at scale, then I would absolutely encourage people to look other more powerful solutions, such as Akka.Tom DuPonthttps://www.blogger.com/profile/08233783264428691459noreply@blogger.comtag:blogger.com,1999:blog-4063545436138319205.post-19835142803613521462016-09-27T07:32:50.143-07:002016-09-27T07:32:50.143-07:00Nice bit of code, thanks!
Whenever I see this sor...Nice bit of code, thanks!<br /><br />Whenever I see this sort of need now, I tend to think of the Actor Model and Akka.NET. The logic of the lambda/action becomes a message and an actor's response to it. You can then automatically put them behind a router of x size and have things processed simultaneously. I find it makes such things much easier to reason about.<br /><br />This is not to discount your solution by any means, but it seemed worth mentioning here.Sean Killeenhttps://www.blogger.com/profile/04420219523879776615noreply@blogger.com