bolha.us

0 posts0 participants0 posts today

henomis🎭 To block or not to block, that is the question.Let’s suppose we have a stream of events and a pull consumer. The consumer has two methods to fetch: the first is gonna block until it receives something, and the second has a timeout to unblock. My personal rule of thumb is:- if you need to synchronously consume a single event then process it: use the blocking one, as you’re using the stream like a FIFO queue. - if you need to fetch ‘n’ events: use the non-blocking one, you might have no warranty that the stream contains (or is able to send) the expected amount of events.<a href="https://mastodon.bsd.cafe/tags/asynchronous" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asynchronous</a> <a href="https://mastodon.bsd.cafe/tags/distributedsystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#distributedsystems</a> <a href="https://mastodon.bsd.cafe/tags/developerslife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developerslife</a>

Mark Gardner<a href="https://social.sdf.org/tags/Microservices" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microservices</a>. Real-time <a href="https://social.sdf.org/tags/asynchronous" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asynchronous</a> processing. <a href="https://social.sdf.org/tags/PostgreSQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PostgreSQL</a> and <a href="https://social.sdf.org/tags/Redis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Redis</a> integrations. And the best damn collection of well-tested <a href="https://social.sdf.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a> libraries.Your company is using the <a href="https://social.sdf.org/tags/Perl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Perl</a> <a href="https://social.sdf.org/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> language and ecosystem, even if you don’t know it.So join Deriv and support <a href="https://fosstodon.org/@metacpan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@metacpan</a> so that your systems can continue to run for the *next* 25 years: <a href="https://www.perl.com/article/why-deriv-supports-the-perl-ecosystem/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.perl.com/article/why-deriv-supports-the-perl-ecosystem/</a><a href="https://fosstodon.org/@metacpan/114162204973000011" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://fosstodon.org/@metacpan/114162204973000011</a>

seadriftGet started with async in Python <a href="https://www.infoworld.com/article/2264616/get-started-with-async-in-python.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.infoworld.com/article/2264616/get-started-with-async-in-python.html</a>"Asynchronous programming, or async, is a feature of many modern languages that allows a program to juggle multiple operations without waiting or getting hung up on any one of them. It’s a smart way to efficiently handle tasks like network or file I/O, where most of the program’s time is spent waiting for tasks to finish." <a href="https://mas.to/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://mas.to/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#python</a> <a href="https://mas.to/tags/asynchronous" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#asynchronous</a>

kute null pointer 🤖I'm learning just a tad-bit about <a href="https://subs4social.xyz/tags/AMD" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> ( <a href="https://subs4social.xyz/tags/asynchronous" rel="nofollow noopener noreferrer" target="_blank">#asynchronous</a> <a href="https://subs4social.xyz/tags/module" rel="nofollow noopener noreferrer" target="_blank">#module</a> <a href="https://subs4social.xyz/tags/dependencies" rel="nofollow noopener noreferrer" target="_blank">#dependencies</a> ) and <a href="https://subs4social.xyz/tags/RequireJS" rel="nofollow noopener noreferrer" target="_blank">#RequireJS</a>. I've always been too retarded to do anything with <a href="https://subs4social.xyz/tags/Webpack" rel="nofollow noopener noreferrer" target="_blank">#Webpack</a>, because it needs to be running server-side as well as clientside in the browser (I think). Dependencies bundled together in real time, at the server side, plus whatever minifier and obfuscation they decide to add. With RequireJS, it just needs to find static JS files in the URL folder structure it expects. So you can use really any webserver.

Recent searches

Search options

Administered by:

Server stats:

#asynchronous