<?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>Segment Archives - The Iron.io Blog</title>
	<atom:link href="https://blog.iron.io/tag/segment/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.iron.io/tag/segment/</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>Wed, 02 Aug 2023 04:50:47 +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>Segment Archives - The Iron.io Blog</title>
	<link>https://blog.iron.io/tag/segment/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Build an ETL Pipeline for ElasticSearch Using Segment and Iron.io</title>
		<link>https://blog.iron.io/how-to-build-etl-pipeline-for/</link>
					<comments>https://blog.iron.io/how-to-build-etl-pipeline-for/#respond</comments>
		
		<dc:creator><![CDATA[Iron]]></dc:creator>
		<pubDate>Thu, 02 Oct 2014 17:00:00 +0000</pubDate>
				<category><![CDATA[Integrations]]></category>
		<category><![CDATA[Serverless Workers & Containers]]></category>
		<category><![CDATA[ETL]]></category>
		<category><![CDATA[IronMQ]]></category>
		<category><![CDATA[IronWorker]]></category>
		<category><![CDATA[Segment]]></category>
		<category><![CDATA[tutorials]]></category>
		<guid isPermaLink="false">http://ironio2.wpengine.com/?p=15</guid>

					<description><![CDATA[<p>Overview ETL is a common pattern in the big data world for collecting and consolidating data for storage and/or analysis. Here's the basic process: Extract data from a variety of sources Transform data through a set of custom processes Load data to external databases or data warehouses   Segment + Iron.io + Elasticsearch = A&#8230;</p>
<p>The post <a href="https://blog.iron.io/how-to-build-etl-pipeline-for/">How to Build an ETL Pipeline for ElasticSearch Using Segment and Iron.io</a> appeared first on <a href="https://blog.iron.io">The Iron.io Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.iron.io/how-to-build-etl-pipeline-for/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Segment.io adds Iron.io as an endpoint for message queueing</title>
		<link>https://blog.iron.io/segmentio-adds-ironio-as-endpoint-for/</link>
					<comments>https://blog.iron.io/segmentio-adds-ironio-as-endpoint-for/#respond</comments>
		
		<dc:creator><![CDATA[Iron]]></dc:creator>
		<pubDate>Mon, 25 Aug 2014 17:16:00 +0000</pubDate>
				<category><![CDATA[Integrations]]></category>
		<category><![CDATA[Serverless Message Queue]]></category>
		<category><![CDATA[IronMQ]]></category>
		<category><![CDATA[Segment]]></category>
		<guid isPermaLink="false">http://ironio2.wpengine.com/?p=24</guid>

					<description><![CDATA[<p>Iron.io + Segment.io = Integration Goodness IronMQ has just been added as an endpoint for message queueing within Segment.io. Segment.io provides a single gateway that lets developers, marketers, and analysts pipe logs, metrics, user actions, and other key app data to hundreds of other applications and tools. The Segment.io API acts as a control for&#8230;</p>
<p>The post <a href="https://blog.iron.io/segmentio-adds-ironio-as-endpoint-for/">Segment.io adds Iron.io as an endpoint for message queueing</a> appeared first on <a href="https://blog.iron.io">The Iron.io Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://blog.iron.io/segmentio-adds-ironio-as-endpoint-for/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
