[tahoe-dev] Tahoe-LAFS as web server file backend?

[Alfonso Montero López]

Hi all.

I was just thinking in a web server redundancy and/or load balancing
scenario, but having a hot-standby server it's another good use case.
It's not a matter of capacity, I would like every web server to have
the entire web root available locally to make it be as performant as
possible. Having remote dircaps mounted someway could be fit for other
applications I can't think of now. By Greg's comment, makes me think
that perhaps tahoe's encryption adds too much overhead and it's an
overkill.
However, Miles made a very good point in another feature I haven't
thought of. Each user's home dir would be just another dircap, and the
entire tahoe architecture would fit beautifully for handling user
separation and security. As tahoe is now, you should trust the users
somehow for space abuse, but that's a WIP in the accounting side. That
makes tahoe's encryption have sense again.
I'm still not sure if what I propose is too much overhead
performace-wise or an overkill approach. Maybe I'm dreaming awake :)

Regards,

--
Alfonso M. L.

2012/12/23 Miles Fidelman <mfidelman at meetinghouse.net>:
> Greg Troxel wrote:
>>
>> Alfonso Montero López <amontero at tinet.org> writes:
>>
>>> Now I'm at another different thing. Thinking in ditributed/clustered
>>> web serving, I wonder what would be the best way to use Tahoe-LAFS as
>>> the file backend, if possible. I mean, you throw a bunch of webservers
>>> at the front, say Apache or nginx and point their webroots to a
>>> locally stored tahoe cap and serve/run files and scripts from there
>>> (PHP, for instance). Let's leave MySQL for another story :)
>>
>> It seems people suggest this from time to time, but I don't understand
>> it.  What problem are you trying to solve?  Do you have more bits to
>> serve on the web than fit on the web server, and you want to use
>> untrusted storage?  Perhaps you could explain your requirements and how
>> that leads you to use tahoe as a back end.
>>
>
> Seems to me that it's a way to truly publish web pages to "the cloud" -
> making storage completely independent of any specific host. Somewhat
> reminiscent of USENET (NNTP actually) in that regard. Publish from anywhere,
> read from anywhere - with NNTP, messages are replicated everwhere, with
> Tahoe, blocks are replicated across multiple servers and then reassembled at
> the reading end.  Not sure what the performance would be like.
>
>
> --
> In theory, there is no difference between theory and practice.
> In practice, there is.   .... Yogi Berra
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>