<?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>dynos Archives - The Iron.io Blog</title>
	<atom:link href="https://blog.iron.io/tag/dynos/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.iron.io/tag/dynos/</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>Tue, 19 Oct 2021 22:39:28 +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>dynos Archives - The Iron.io Blog</title>
	<link>https://blog.iron.io/tag/dynos/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Worker Dynos vs Worker add-ons</title>
		<link>https://blog.iron.io/worker-dynos-vs-worker-add-ons/</link>
					<comments>https://blog.iron.io/worker-dynos-vs-worker-add-ons/#respond</comments>
		
		<dc:creator><![CDATA[Nick]]></dc:creator>
		<pubDate>Mon, 04 Oct 2021 09:15:00 +0000</pubDate>
				<category><![CDATA[Serverless Computing]]></category>
		<category><![CDATA[add-ons]]></category>
		<category><![CDATA[dynos]]></category>
		<category><![CDATA[Heroku]]></category>
		<category><![CDATA[Heroku Dyno]]></category>
		<category><![CDATA[IronWorker]]></category>
		<category><![CDATA[worker]]></category>
		<guid isPermaLink="false">https://blog.iron.io/?p=8477</guid>

					<description><![CDATA[<p>Heroku is a cloud platform offered as a service. It lets you deploy and manage applications without worrying about the infrastructure. Heroku is a polyglot platform that supports most of the standard frameworks and languages like Python, Java, Node.js, Ruby, etc. Heroku uses the Git version control system as the primary way of deploying applications. &#8230;</p>
<p>The post <a href="https://blog.iron.io/worker-dynos-vs-worker-add-ons/">Worker Dynos vs Worker add-ons</a> appeared first on <a href="https://blog.iron.io">The Iron.io Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.iron.io/worker-dynos-vs-worker-add-ons/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>IronWorker vs. Dynos</title>
		<link>https://blog.iron.io/ironworker-vs-dynos/</link>
					<comments>https://blog.iron.io/ironworker-vs-dynos/#respond</comments>
		
		<dc:creator><![CDATA[Nick]]></dc:creator>
		<pubDate>Wed, 23 Dec 2020 01:47:00 +0000</pubDate>
				<category><![CDATA[Serverless Workers & Containers]]></category>
		<category><![CDATA[containers]]></category>
		<category><![CDATA[dynos]]></category>
		<category><![CDATA[Heroku]]></category>
		<category><![CDATA[IronWorker]]></category>
		<guid isPermaLink="false">https://blog.iron.io/?p=7754</guid>

					<description><![CDATA[<p>Overview Architecture: IronWorker is a hosted job processing solution that lets you manage container-based workloads. Dynos are isolated Linux containers in Salesforce Heroku that facilitate code based on various commands. Purpose: Use dynos to execute code for specific commands. Use IronWorker to manage and schedule these containers. Scalability: Both IronWorker and dynos scale but in different ways.&#8230;</p>
<p>The post <a href="https://blog.iron.io/ironworker-vs-dynos/">IronWorker vs. Dynos</a> appeared first on <a href="https://blog.iron.io">The Iron.io Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.iron.io/ironworker-vs-dynos/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
