Originally Posted by
MoanaLisa
The problem is not so much the size of the build. The real task is preserving every element of the environment that it runs in as well. I alluded to that in my other post but it's not even close to enough to just have the code for the build. You have to have:
1. OS version, patch and build (for the correct flavor of Unix if that's what it runs on)
2. Database build (with associated OS and 3rd party tools that match)
3. Compatible or compliant hardware that will deliver the I/O in precisely the right way so I/O tuning remains appropriate. Not too slow or fast which can lead to overflow issues.
4. Client build which in itself has different requirements depending on age and OS (This they likely do have).
5. Correct builds for 3rd party tools for code and object maintenance (C/C++/whatever else they use), development and modification.
6. Miscellaneous other things that must be in sync with all of the above to bring it up in a professional way and maintain it properly.
I think that's the thing that most people don't understand although they should. You can't run a lot of DOS games easily in Windows 7 and this is that on a much larger and immensely more complicated scale. And that's assuming that the 'engine' that people like to talk about is considered as part of the server piece. It doesn't necessarily need to work that way because I can easily imagine minor changes to the engine that might not require a different game/client build (but likely in reality would).
I won't go into my real life very much but my current gig is auditing IT departments that are trying to either qualify or maintain compliance for ISO/JSOX certification. What we're talking about here is part and parcel of that. The idea frequently expressed that small/large IT shops--usually running anywhere from a few to dozens if not hundreds of servers many on different OS's and versions of OS's, with hundreds if not thousands of apps large and small, both inhouse and externally created all of different ages, many of which were developed in languages ranging from C, C++, Java, various versions of Basic, well the list goes on all the way back to FORTRAN and COBOL, with many of them talking or exchanging information with one another--can roll back to any previous IT environment easily is quite false. So too, this. Just my two cents based on being in the enterprise application business for a long time.
EDIT: Sorry for the length and tangled-up language. It's really a subject for a 20-page paper and suffers from too much compression. But I think I've conveyed the idea. At least a little bit.