<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Concurrency on</title><link>/tags/Concurrency/</link><description>Recent content in Concurrency on</description><generator>Hugo</generator><language>en</language><managingEditor>doppelganger113@gmail.com (Marko Kovačević)</managingEditor><webMaster>doppelganger113@gmail.com (Marko Kovačević)</webMaster><lastBuildDate>Sun, 27 Oct 2024 05:00:00 +0200</lastBuildDate><atom:link href="/tags/Concurrency/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating notification workers in Java</title><link>/posts/building-notification-workers-in-java/</link><pubDate>Sun, 27 Oct 2024 05:00:00 +0200</pubDate><author>doppelganger113@gmail.com (Marko Kovačević)</author><guid>/posts/building-notification-workers-in-java/</guid><description>&lt;p&gt;An exercise for practicing concurrency where we will use &lt;code&gt;LinkedBlockingQueue&lt;/code&gt; with single worker (thread) per
job type (key) to trigger work in a non-blocking way and also try out the &lt;code&gt;Semaphore&lt;/code&gt;. Imagine publish/subscribe
but without queuing and only doing 1 job at a time, but without any externals like Redis, RabbitMQ and so on,
only Java.&lt;/p&gt;</description></item><item><title>Rise of concurrency</title><link>/posts/rise-of-concurrency/</link><pubDate>Mon, 12 Aug 2024 04:00:00 +0200</pubDate><author>doppelganger113@gmail.com (Marko Kovačević)</author><guid>/posts/rise-of-concurrency/</guid><description>&lt;p&gt;Concurrent programming has been out there for quite some time, take for example &lt;a href="https://www.erlang.org" target="_blank" rel="noopener noreffer "&gt;Erlang&lt;/a&gt; (1986.)
and &lt;a href="https://lua.org" target="_blank" rel="noopener noreffer "&gt;Lua&lt;/a&gt; (1993.) languages, but there is a period after 2012. or so, which, from my experience, seemed to
receive the most evolutions in the land of web server concurrency development due to the increased requirement for
efficiency and resilience.&lt;/p&gt;</description></item></channel></rss>