Your skill will accomplish what the force of many cannot |
|
PerlMonks |
Re: Twin interfaces, and one and a half databases to a projectby Anonymous Monk |
on Aug 17, 2002 at 22:42 UTC ( [id://190928]=note: print w/replies, xml ) | Need Help?? |
Depends a lot on the exact boundary for the split... if it's a simple 'these tables are billing, these tables are customer accounts', then why not use two different DBs? The customer webserver only has access to the DB with customer-modifiable data, and the administrator's webserver has access to both DBs. Couple of different ways to split it, based on paranoia level:
Trying to keep a copy of the customer account data in the administrative DB as well seems unnecessary. It won't kill you to have the administrative interface dealing with two different databases. Hope this helps... Jeremy Weatherford
I guess I should register here eventually...
In Section
Meditations
|
|