Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I asked because it wasn't clear form the website. The tagline says file sync, what details there were said distributed filesystem.

So, for example, the total data stored and accessible in the system can exceed the local storage size of any individual participating node?

What's the performance like? (A sync service will be as fast, or slow, as local storage, but a distributed system can be a lot faster, or slower.)

How are you handling it when nodes which were previously added to the system are unavailable? For example, a user with a desktop and a laptop who stores a pile of data on the system, what happens when the desktop is off? Do you have control over what data is available on the laptop, and what happens when you try and access data which is currently unavailable?



To echo your update on the original question: while AeroFS is a distributed filesystem with quite complicated mechanisms underneath, we work very hard to make AeroFS dead simple to use. Following this philosophy, we've implemented the features that you mentioned but they're currently disabled/hidden for the sake of simplicity.

Regarding offline computers: if the only computers that host a file are offline, the file data will be unavailable. Currently, offline files are invisible in Finder/Explorer/etc. Because the current system only supports full replication, having offline files should be a rare case.

Regarding performance: it's crucial to us. Lots of efforts has been made (and even more to be made) to ensure the filesystem has comparable performance to local storage; sync performance is another area that we invest a lot of time in.


Only full replication. So not a good idea for small devices.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: