Isolation of Database access from users. For example you set up a partition in zone A with all of your databases. Zone B has your application server, and Zone C is your user workstations. You have 1 firewall defined between Zone A and B. (Could be server based with virtual private buss level IP interface or physical using an Ethernet adapter.) You then have a second firewall between workstations in Zone C and the Application server in Zone B. Users can only access the application server and not reach through to the database server.
This is very secure and not normal. (My boss wanted that here and in his 5 years here, has not implemented it.)
This is on top of what Trevor mentioned.
Generally I see the programmers using one server for application and database with a second environment for staging where the application and database servers are isolated. Then the production environment.
We here provide separate hardware for our customer faced applications / database which sit behind a firewall and a web interface.
internet - firewall - web server - firewall - application / database server.
Director of Information Services
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Briggs, Trevor (TBriggs2)
Sent: Monday, June 09, 2014 10:04 AM
To: Midrange Systems Technical Discussion
Subject: RE: Why do companies partition their Power Servers?
Two examples from my experience are to separate production from
development and to isolate a partition running a web server (accessible
from the outside world) from production data.