This is a pretty simple idea - a boss thread assigns work to a pool of worker threads who do nothing until some work enters their queue. This way the boss can fill a queue very quickly and you have multiple back end processes that can consume that queue.
I'm using threading and not an async thing because some of the work I'll be assigning to threads are long-polling operations. The workers will hit some REST API route on some other application, and some of those routes take up to 30 seconds to complete or have dependencies or followup work. Rather than block and spin in an async call,…
I've been lurking here for months - there are some serious experts that blog here, along with a few absolute newbies. I figured my experience level didn't matter. I could have blogged elsewhere too....But...
I'll admit that part of the reason I chose to write my blog here is due to the recent amount of posts I've seen over Sexual Harrassment and what it means to be a Member of a Community that has standards. The more voices in a community speak out, the more the community *is* those voices.
I won't post anything else about it - this isn't 'my community' in that I don't attend …
I use perl, at home, at work, and I've been using it for over a decade. I recently switched job titles and had to relearn The Web outside of the old CGI forms that I used to know back in the crusty old days of web 1.0.
Handrolled mysql connections and 50k lines of code aren't good practice anymore - not that they ever were, but it was at least accepted and common practice. I've started using MongoDB as well, and its collection of documents metaphor makes a lot of sense when you can pair JSON and perl data types so easily.
Perl has moved on since the early 5.008 days, but the …
I stuff with perl and stuff.