|
The single database was my point. Why wouldn't you split databases and have customer data in one (additionally for increased security of customer's personal data) and handle the file storage/website side of the equation so that a single point of failure won't compromise everything.
Email down for several hours is bad enough, but having ones website down at the same time is even worse.
I seem to remember some commercial webmail applications advising this approach ...
|