4 ms·
In a small team there should be single development database restored from backup. That development database should be hosted on development server, not on deve
by dennisgorelik 12y ago
In a small team there should be single development database restored from backup.
That development database should be hosted on development server, not on developers' laptops.
Developers are welcome to VPN into corporate network from their laptops in order to work with database.
Any other issues?
- collyw 12y agoThat doesn't make sense. What if people want to change the database schema, and 4 developers are working on it at once?
- opendais 12y agoWhat we do at work is every developer has their own VM on an on-premise server in a locked room that is rebuilt/destroyed as needed with the full stack. So maybe he just wasn't being clear?
- dennisgorelik 12y agoBreaking database changes do not happen often. There could be multiple solutions to that: 1) Other developers wait. 2) Affected functionality is turned off while in transition. 3) Changes implemented in a non-breaking way. 4) Change is done quickly. 5) Separate database environment is setup in order to prepare change. In any case, the harder problem is to deploy that database change into production when thousands of users are working on it at once. Practicing that change in development environment helps to make production deployment smoother.
- collyw 12y agoFair enough, I am guessing your work is at a different scale from mine. We are "super agile" (constantly changing) due to the changing nature of the sequencing technology we work with.