[Kroupware] FAQ: flexible administration of multiple kolab servers

[Andreas Jellinghaus]

dns can be very fast and effective.

i think the djbns has one file per value?
and a filesystem like ext2/3 with the new hashes or reiserfs
can handle that very well.

any db file or similiar storage (used in ldap and sql servers) is also
fast. and even though i don't know the bind internals, i guess it is
reasonable fast, too, since the domain server are run with million
domains.

bu i heard storries about bind loading .com and similiar domians
requireing hours? so i guess  bind/dns is not meant as a flexible
solutions. big zones like .de or .com reload once every 24h?


on the other side i now big providers using a two stage model:
first stage accepts connections, caches, etc. and then
communucates with a second stage, a storage server.

the first stage is usualy managed with loadbalancers or round robin.

also the first/second stage concept is nice when it commes to
moving data: the first stage can block for a while,
till the move is completed. i don't know how anyone would
handle moving data in a single stage system, I'd be interested to hear.

andreas