|
Hi,
I just discovered that a client has done this:
They have two web applications A1 and A2. They have seperate hostnames/URLs. Both have a production and a test database A1p and A1t/ A2p and A2t. What they've done is have both A1p and A2p on the same actual databaser server and A1t and A2t on the same server.
So, I'm thinking - if a bug in application A1 crashes the application and database badly it will risk bringing down both services A1 and A2. The same risk would be evident on a successful security breach.
I would prefer to A1p and A2p on seperate servers, maybe keeping A1t and A2t on the same. (This is what seems to be happening when the database servers are being repladed).
What is the general thought on the current setup?
/M ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ============================================================================================================================ |
