A better implementation will be different deadlines according to the 1st letter of the family name. This will prevent huge overloading near , and at the deadline.
i am no expert in this area. IRAS's system capacity is 20,000 taxpayers a day, after the initial hiccups. does it looks like a 'probably a cheap skate IT architecture implementation'?
SLA? Interesting question. If you are a vendor building the solution, as $X and the customer tells you: "We expect peak of 20,000 users." Would you max out your budget to cater for more, say 40k? Or would you max you profit and design a solution for 20,000 users (say with 10% slack) knowing that the customer would sign off for the 20k users?
BTW, I filed about 21 hours ago. Pretty smooth sailing.
Watcher, the problem is SLA is never considered AFTER signing, clients want to see the system running, the solutionists wants to get the final payment. Simple as that.
For me, definitely will provide a solution for 20K peak. The earnings come when the client instructs the developers to now up it to 50K, which should be scalable and NOT development anymore. heehee.