From a security standpoint, developers should not deploy, install, manage, or administer any production servers. It is a conflict of interests and is covered by separation of duties.
That being said, I've worked in many environments. In my current position we have four teams.
1) Development 2) System Administrators 3) Application Administrators 4) Database Administrators
Development develops the applications, System administrators manage and maintain the hardware/os, app admins manage and maintain the applications, and the dbas manage and maintain the databases.
Development writes the applications and hands them off to the application administrators. These guys install the app in our QA environment and go through some testing. Once it's tested internally, we install it in UAT and give our customers a chance to test. If there are any problems during testing, the release goes back to development. Once everything has tested clean, we have a change control meeting with the DBAs, App admins, and System admins to discuss all of the moving parts and work together to put everything into production.
I think we have the best of both worlds. Development is out of the loop after they hand off the product, but we also have Application support folks which work closely with development and know the applications and their requirements.
I've got no problems working with sun hardware. It's actually pretty easy. On the systems with DR it is pathetically easy to hot swap a CPU or I/O board without taking the machine down..
Try working with real sun hardware instead of sparc twenties. Even a 4500 sitting on a shelve is easily accessable..
I used to work for Apple, and I know first hand that Apple forces resellers to their pricing structure.. You won't find any apple products for less than they sell for at the apple store.
This is pretty funny - look at the amount of bandwidth on a quad proc Intel box, and a quad proc sun machine, they're not even close. There's NO WAY an intel machine can handle the disc and ram IO a sun machine can. I'd like to see you put 192GB of ram into an intel machine.
We're not even going to get into alternate pathing...
I had a girlfriend who played this game, she was SO caught up in it, I mean she played it day and night, I still to this day do not know WHY. The game is SO boring, and ignorant. yet, she loves it dearly.
Remember, firewire is not 400MBYTES a second, but 400MBITS a second. This is about ~40MBYTE/S. Which is still as fast as UltraWide SCSI. While this is not slow, it is not the lightening fast solution it's made out to be.
Slashdot Mirror
From a security standpoint, developers should not deploy, install, manage, or administer any production servers. It is a conflict of interests and is covered by separation of duties.
That being said, I've worked in many environments. In my current position we have four teams.
1) Development
2) System Administrators
3) Application Administrators
4) Database Administrators
Development develops the applications, System administrators manage and maintain the hardware/os, app admins manage and maintain the applications, and the dbas manage and maintain the databases.
Development writes the applications and hands them off to the application administrators. These guys install the app in our QA environment and go through some testing. Once it's tested internally, we install it in UAT and give our customers a chance to test. If there are any problems during testing, the release goes back to development. Once everything has tested clean, we have a change control meeting with the DBAs, App admins, and System admins to discuss all of the moving parts and work together to put everything into production.
I think we have the best of both worlds. Development is out of the loop after they hand off the product, but we also have Application support folks which work closely with development and know the applications and their requirements.
Why yes, yes I have.
I've got no problems working with sun hardware. It's actually pretty easy. On the systems with DR it is pathetically easy to hot swap a CPU or I/O board without taking the machine down..
Try working with real sun hardware instead of sparc twenties. Even a 4500 sitting on a shelve is easily accessable..
I used to work for Apple, and I know first hand that Apple forces resellers to their pricing structure.. You won't find any apple products for less than they sell for at the apple store.
They're doing it via their http://proxy:8080
This is pretty funny - look at the amount of bandwidth on a quad proc Intel box, and a quad proc sun machine, they're not even close. There's NO WAY an intel machine can handle the disc and ram IO a sun machine can. I'd like to see you put 192GB of ram into an intel machine.
We're not even going to get into alternate pathing...
I had a girlfriend who played this game, she was SO caught up in it, I mean she played it day and night, I still to this day do not know WHY. The game is SO boring, and ignorant. yet, she loves it dearly.
Some things are best left unknown.
Remember, firewire is not 400MBYTES a second, but 400MBITS a second. This is about ~40MBYTE/S. Which is still as fast as UltraWide SCSI. While this is not slow, it is not the lightening fast solution it's made out to be.