<?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>Heroku Dyno Archives - The Iron.io Blog</title>
	<atom:link href="https://blog.iron.io/tag/heroku-dyno/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.iron.io/tag/heroku-dyno/</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>Heroku Dyno Archives - The Iron.io Blog</title>
	<link>https://blog.iron.io/tag/heroku-dyno/</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>Know All About Autoscaling On Heroku</title>
		<link>https://blog.iron.io/know-all-about-autoscaling-on-heroku/</link>
					<comments>https://blog.iron.io/know-all-about-autoscaling-on-heroku/#respond</comments>
		
		<dc:creator><![CDATA[Nick]]></dc:creator>
		<pubDate>Mon, 13 Sep 2021 09:45:00 +0000</pubDate>
				<category><![CDATA[Serverless Computing]]></category>
		<category><![CDATA[Auto-scaling]]></category>
		<category><![CDATA[Autoscaling]]></category>
		<category><![CDATA[Heroku]]></category>
		<category><![CDATA[Heroku Dyno]]></category>
		<category><![CDATA[IronWorker]]></category>
		<guid isPermaLink="false">https://blog.iron.io/?p=8457</guid>

					<description><![CDATA[<p>Autoscaling is a method used to manage the traffic on the network. When the outbound traffic on average is higher or lower, in each instance, the default triggers dynamically tend to autoscale and adjust the computational resources to meet the demand - typically, the number of servers that manage the load of the application.  So,&#8230;</p>
<p>The post <a href="https://blog.iron.io/know-all-about-autoscaling-on-heroku/">Know All About Autoscaling On Heroku</a> appeared first on <a href="https://blog.iron.io">The Iron.io Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.iron.io/know-all-about-autoscaling-on-heroku/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>IronWorker CaaS Worker: Heroku Dyno Setup</title>
		<link>https://blog.iron.io/ironworker-caas-worker-heroku-dyno-setup/</link>
					<comments>https://blog.iron.io/ironworker-caas-worker-heroku-dyno-setup/#respond</comments>
		
		<dc:creator><![CDATA[Nick]]></dc:creator>
		<pubDate>Fri, 30 Apr 2021 09:02:00 +0000</pubDate>
				<category><![CDATA[Integrations]]></category>
		<category><![CDATA[caas]]></category>
		<category><![CDATA[Heroku Dyno]]></category>
		<category><![CDATA[integration]]></category>
		<category><![CDATA[IronWorker]]></category>
		<category><![CDATA[Setup]]></category>
		<guid isPermaLink="false">https://blog.iron.io/?p=8306</guid>

					<description><![CDATA[<p>In this article, we will tell you the steps you need to set up Heroku Dyno for IronWorker. Setup Outline: Create a Heroku App Install Heroku CLI Deploy Your App Costs Notes Security Pros &#38; Cons 1. Create a Heroku App On your Heroku dashboard, click on “Create new app”, specify the app name and&#8230;</p>
<p>The post <a href="https://blog.iron.io/ironworker-caas-worker-heroku-dyno-setup/">IronWorker CaaS Worker: Heroku Dyno Setup</a> appeared first on <a href="https://blog.iron.io">The Iron.io Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.iron.io/ironworker-caas-worker-heroku-dyno-setup/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
