[Tilesathome] Distributed server idea

[Frederik Ramm]

Hi,

>> * Central server ("Load server") - really only one big DNS server
>> that contains a database with one entry per tileset, pointing to IP
>> number of server carrying that tile; perhaps also records
>> alternatives and does availability checks/round robin; accepts
>> notifications from tile servers
>
> Instead of per-tile maybe its more easy per-blocks or zones or  
> whatever,
> It will decrease the load of this "Load server" because the querys are
> in a small set

But this would require pre-arranging and defining the zones. If you  
have one DNs entry per tileset, then you can set up your own tile  
server, serve two tiles, announce them to the central server and be  
the authoritative source for  those two tiles within minutes. This is  
not possible with per-block or per-zone or whatever assignment, you  
would have to take over a whole block/zone or submit your tiles to  
the server serving that block/zone.

>> * Create the custom DNS server we'll need for the Load Server. This
>> is definitely a C/C++ task. Needs MySQL as a backing store but must
>> keep all addresses in memory. Should be doable with a sub-200 MB
>> memory footprint. Cannot use bind. Database-backed DNSes exist; would
>> have to check if they can be told to also have big memory cache.
>
> djbdns, in a per-block schema we dont need mysql as backing store, a
> simple text file will be enough

Depends on the number of blocks probably and how fast-changing they  
are. I was assuming to have a highly dynamic environment where one  
tileset would be hosted here now and there the next minute...

Bye
Frederik

-- 
Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00.09' E008°23.33'