<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Distributed Tasks in Python on Melted in Hex</title>
    <link>https://meltedinhex.com/tags/distributed-tasks-in-python/</link>
    <description>Recent content in Distributed Tasks in Python on Melted in Hex</description>
    <image>
      <title>Melted in Hex</title>
      <url>https://meltedinhex.com/images/og-social.png</url>
      <link>https://meltedinhex.com/images/og-social.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 12 Jan 2017 23:30:00 +0530</lastBuildDate>
    <atom:link href="https://meltedinhex.com/tags/distributed-tasks-in-python/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Distributed processing using celery in python</title>
      <link>https://meltedinhex.com/posts/distributed-processing-using-celery-in/</link>
      <pubDate>Thu, 12 Jan 2017 23:30:00 +0530</pubDate>
      <guid>https://meltedinhex.com/posts/distributed-processing-using-celery-in/</guid>
      <description>&lt;p&gt;Celery is an asynchronous task queue based on distributed message passing. Tasks are executed concurrently on one or more worker servers using multiprocessing, Eventlet or gevent. Tasks can execute asynchronously (in the background) or synchronously (wait until ready).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Architecture:&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://meltedinhex.com/images/distributed-processing-using-celery-in/celery_architecture-d8d5269c.jpg&#34;&gt;&lt;img loading=&#34;lazy&#34; src=&#34;https://meltedinhex.com/images/distributed-processing-using-celery-in/celery_architecture-d8d5269c.jpg&#34;&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Fig1 : Celery architecture&lt;/p&gt;
&lt;p&gt;The main part of this architecture is the broker (transporter), which handles all the task processing.&lt;/p&gt;
&lt;p&gt;The client sends tasks to the broker, and the broker uses round robin to distribute those tasks to workers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
