On the local distro repo thing: updates no longer count against your bandwidth quota, so the only advantage would be performance. Already, apt-get update seems to be mostly I/O-bound (and apt-get upgrade is mostly installing-packages), and yum update is just plain slow as snails no matter how close the repo is. If Linode had 1.2 TB lying around doing nothing, I'd prefer it exported by NFS and mountable as scratch space
(Source of 1.2 TB figure:
http://mirrors.rit.edu/dirsizes.txt, centos+debian+ubuntu. Also, as a paying customer of .rit.edu and of .gov, feel free to use mirrors.rit.edu or mirror.anl.gov. They're really fast. Tell them I sent you.)
taligent wrote:
Please consider build a Cloudflare/Firewall product that can filter out all of the bad guys before it hits my delicate app servers.
Hmm... perhaps a caching layer as part of NodeBalancer? The underlying high-availability architecture is already there, and it functions as a firewall, albeit a rather special-purpose one.
_________________
Code:
/* TODO: need to add signature to posts */