11:23 a.m.
Hey! Cool idea and thanks for sharing the kind words.
Let's explore this ...
So, as I understand load balancing, it requires a piece of software that
receives HTTP requests and it makes a decision about where to route that
request based on an algorithm. An example of an algorithm is, route to
the web server that has the least amount of connections.
The first thing that comes to mind is: does load balancing require this
"central" first point of contact? And if so, who will provide the power
for that! ;) This brings along the "always online" needs, centralisation
of point of failure and a place to look at everyone's metadata, etc.
I must ask: is the idea of load balancing itself an "always online" hangover!?
RE: bittorrent, that's a nice idea too. I also thought about the DAT
protocol and it has a nice section on the considerations between:
https://docs.datproject.org/docs/faq#how-is-dat-different-than-academic-t...
Where it points to the drawback of "BitTorrent is for sharing static
files, that is, files that do not change over time." for website
content.
So, with DAT (or something similar), we would be downloading copies of
each others websites to our own computers and serving them locally. That
kind of makes sense to me as a nice approach.
If I had to guess at the considerations ...
* Content is changing, so needs to handle syncing / updating
* Needs to be redundant if one server goes down ("offline first")
* Needs to be discovered without central authority (DNS)
* Should be performant for lower bandwidths
* ???
Then to map those considerations onto a protocol ...
Interested to hear further thoughts!
Luke
On 0, Amos Blanton <amos.blanton(a)gmail.com> wrote:
Greetings list -
Inspired by the great low powered server described on the lowtechmagazine
website, I'm interested in setting up a home solar powered server for my
personal website. I set up a webserver on a raspberry pi and made [1]an
instructable about it long ago.
While I appreciate the need to accept some downtime, I wonder if folks on
this list have thought about strategies for federating solar powered
servers to share load? Up here in Denmark I have a great deal of daylight
at the moment - maybe 18 hours or so. If I could mirror other small sites,
and serve them when their hosts are low on batteries, I'd be happy to do
it. And I could use the same sort of help when winter comes.
I wonder if anyone here has considered creating a solar-energy load
balancing service. Members would get mirrorred in other member's
locations, and report their remaining battery capacity / charging status
to the balancer. The load balancer could then route requests to whoever
has the most charge / active sunlight at the moment. Or perhaps there is a
strategy that would use something like the bittorrent protocol to server
websites?
Interesting in any thoughts you have. And thanks for making and sharing
such excellent documentation!
Amos
--
[2]http://amosamos.net
References
Visible links
1. https://www.instructables.com/id/Host-your-own-blog-from-a-25-Raspberry-P...
2. http://amosamos.net/
_______________________________________________
HBSC mailing list -- hbsc(a)we.lurk.org
To unsubscribe send an email to hbsc-leave(a)we.lurk.org