<div dir="ltr"><div>in object stores you sacrifice the consistency gauranteed by filesystems for **higher** availability. probably by "scale" you mean higher availability, so... the answer is probably object storage. <br>
<br>That said, gluster is an interesting file system in that it is "object-like" --- it is really fast for lookups.... and so if you aren't really sure you need objects, you might be able to do just fine with gluster out of the box.<br>
<br>One really cool idea that is permeating the gluster community nowadays is this "UFO" concept, -- you can easily start with regular gluster, and then layer an object store on top at a later date if you want to sacrifice posix operations for (even) higher availability.</div>
<div><br>"Unified File and Object Storage - Unified file and object storage
allows admins to utilize the same data store for both POSIX-style mounts
as well as S3 or Swift-compatible APIs."
(from <a href="http://gluster.org/community/documentation/index.php/3.3beta">http://gluster.org/community/documentation/index.php/3.3beta</a>)<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 9, 2013 at 10:57 AM, Randy Breunling <span dir="ltr"><<a href="mailto:rbreunling@gmail.com" target="_blank">rbreunling@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>From any experience...which has shown to scale better...a file system or an object store?<br><br></div>
--Randy<br>San Jose CA<br></div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br><br clear="all"><br>-- <br>Jay Vyas<br><a href="http://jayunit100.blogspot.com" target="_blank">http://jayunit100.blogspot.com</a>
</div>