<?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>IPHere &#187; Scality</title> <atom:link href="https://www.iphere.com/tag/scality/feed" rel="self" type="application/rss+xml" /><link>https://www.iphere.com</link> <description>We show your current IP</description> <lastBuildDate>Wed, 03 Aug 2022 14:13:56 +0000</lastBuildDate> <language>en-US</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.6.1</generator> <item><title>Scality: Climbing The Cloud Storage Heights</title><link>https://www.iphere.com/scality-climbing-the-cloud-storage-heights</link> <comments>https://www.iphere.com/scality-climbing-the-cloud-storage-heights#comments</comments> <pubDate>Sun, 26 Jun 2011 02:13:59 +0000</pubDate> <dc:creator>IPHere</dc:creator> <category><![CDATA[General]]></category> <category><![CDATA[Climbing]]></category> <category><![CDATA[Cloud]]></category> <category><![CDATA[Heights]]></category> <category><![CDATA[Scality]]></category> <category><![CDATA[Storage]]></category> <guid
isPermaLink="false">http://www.iphere.com/scality-climbing-the-cloud-storage-heights</guid> <description><![CDATA[The traditional storage business models of NAS and SAN have been worthwhile for many enterprises, but the question remains: Is NAS or SAN best for cloud computing environments? Scality, a storage vendor, asserts that, in many cases, the answer is no. Scality&#8217;s RING &#8220;organic storage software&#8221; is, according to the company, the first object-based storage [&#8230;]]]></description> <wfw:commentRss>https://www.iphere.com/scality-climbing-the-cloud-storage-heights/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>