3 ms·
"Two developers would stomp all over each other trying to modify the same piece of code on a production server." Yes, but it's trivial to create both developer
by tomkarlo 15y ago
"Two developers would stomp all over each other trying to modify the same piece of code on a production server."
Yes, but it's trivial to create both developer instances and an integ instance of Rails/Django/PHP so you don't end up trying to both modify code on the production server. Doing that with the db, especially if you want to test against "production scale" data sets, is at the very least going to be expensive.
- IgorPartola 15y agoAre you suggesting having one production DB => multiple virtual machines with application code? If so, I suppose that might work for some read-only workloads. If you need to bring up a "production scale" server for a developer to go along with their virtual machine with application code, then you have to do it no matter what environment the application code runs in. I imagine modifying data using experimental code on a production system is not really desirable no matter what the code is written in.
- tomkarlo 15y agoNo, I'm not suggesting that. But having say 3-4 DBs for integ, testing and production is a long way from having one for each developer.