Slashdot Mirror
Infrastructure for One Million Email Accounts?
cfsmp3 asks: "I have been asked to define the infrastructure for the email system for a huge company, which fed up of Exchange, wants to replace their entire system with something non-Microsoft. I have done this before, but not for anything of this scale. Suppose you are given a chance to build from scratch an email system that has to support around one million accounts. Some corporate, some personal, some free. POP, IMAP, webmail, etc are requirements. The system must scale perfectly, 99.9% uptime is expected... where would you start?"
With an Ask Slashdot Question?
"It's not like your minds are as open as the source you love..." - Me to the majority of Slashdot.
If I was your boss and found out your idea to architecting what will be a large investment, high uptime demands and a large user base was to ask slashot your arse would feel my boot followed closely by the pavement. This sounds like a pretty poorly run place, if you need to ask slashdot for this scale of thing then you are far better off not touching it.
HawtMaule ruins on FreeBSHD
99.9% Uptime allows for 86.4 seconds of downtime daily. So that's approximately 1.5 minutes of downtime a day or 8.76 hours of downtime a year. I doubt this would go noticed unless all or a good deal of those 8.76 hours happened in one day or one week. You are suggesting a 99.999% uptime rating or 0.864 seconds of downtime a day, or just 5.256 hours of downtime a year. Sorry, that's just not realistic. Your UPS will most likely fail before that kind of uptime is achieved. 3 nines are sufficient. Check my math if you want: 100.00% - 99.90% = 0.1% = 0.001 24 * 60 * 60 = 86400 (seconds in a day) 0.001 * 86400 = 86.4 (seconds of downtime a day) 86.4/60 = 1.44 (minutes of downtime a day) 1.44 * 365 = 525.6 (minutes of downtime a year) 525.6/60 = 8.76 (hours of downtime a year)
-illumina+us "I put on my robe and wizard hat..."
dude... you rule...
batman beyond was definately the best one.