<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Task Processing Archives - The Iron.io Blog</title>
	<atom:link href="https://blog.iron.io/tag/taskprocessing/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.iron.io/tag/taskprocessing/</link>
	<description>Scalable serverless application tools to run background tasks with Docker containers and manage messaging queues with cloud elasticity and handheld customer support.</description>
	<lastBuildDate>Fri, 10 Sep 2021 10:20:38 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://blog.iron.io/wp-content/uploads/2017/11/cropped-iron-avatar-1-32x32.png</url>
	<title>Task Processing Archives - The Iron.io Blog</title>
	<link>https://blog.iron.io/tag/taskprocessing/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Asynchronous Task Processing With Heroku</title>
		<link>https://blog.iron.io/asynchronous-task-processing-with-heroku/</link>
					<comments>https://blog.iron.io/asynchronous-task-processing-with-heroku/#respond</comments>
		
		<dc:creator><![CDATA[Nick]]></dc:creator>
		<pubDate>Mon, 13 Sep 2021 10:11:00 +0000</pubDate>
				<category><![CDATA[Serverless Computing]]></category>
		<category><![CDATA[Asynchronous tasks]]></category>
		<category><![CDATA[Heroku]]></category>
		<category><![CDATA[iron.io]]></category>
		<category><![CDATA[IronMQ]]></category>
		<category><![CDATA[Task Processing]]></category>
		<guid isPermaLink="false">https://blog.iron.io/?p=8453</guid>

					<description><![CDATA[<p>Before exploring Asynchronous Task Processing With Heroku, we must understand what Asynchronous task processing is.  Asynchronous means you can execute numerous things at once and do not have to wait for one thing to end to unblock the other. You work in sync and work on several things simultaneously.   That’s the goal of the asynchronous&#8230;</p>
<p>The post <a href="https://blog.iron.io/asynchronous-task-processing-with-heroku/">Asynchronous Task Processing With Heroku</a> appeared first on <a href="https://blog.iron.io">The Iron.io Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.iron.io/asynchronous-task-processing-with-heroku/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Asynchronous Task Processing in Cloud</title>
		<link>https://blog.iron.io/asynchronous-task-processing-in-cloud/</link>
					<comments>https://blog.iron.io/asynchronous-task-processing-in-cloud/#respond</comments>
		
		<dc:creator><![CDATA[Nick]]></dc:creator>
		<pubDate>Mon, 13 Sep 2021 07:35:00 +0000</pubDate>
				<category><![CDATA[Serverless Computing]]></category>
		<category><![CDATA[Asynchronous tasks]]></category>
		<category><![CDATA[cloud tasks]]></category>
		<category><![CDATA[Iron]]></category>
		<category><![CDATA[Task Processing]]></category>
		<guid isPermaLink="false">https://blog.iron.io/?p=8442</guid>

					<description><![CDATA[<p>When you have an application that processes data with sizes ranging from small to large and if your system processes them one by one, there is a high chance that one of the tasks fails. This could lead to application breakage or high latency due to retry.  &#160; Imagine, you are now pushing the computing&#8230;</p>
<p>The post <a href="https://blog.iron.io/asynchronous-task-processing-in-cloud/">Asynchronous Task Processing in Cloud</a> appeared first on <a href="https://blog.iron.io">The Iron.io Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.iron.io/asynchronous-task-processing-in-cloud/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
