4 ms·
> You only need one development database. You do not need one per dev. That's just wasteful of computing resources. Ideally, every developer would be able to h
by nanis 5y ago
> You only need one development database. You do not need one per dev. That's just wasteful of computing resources.
Ideally, every developer would be able to have separate dev environments per branch in which they can work independently. And, yes, that means a suitable dev database which you can create and destroy at will.
The benefits of this are independent of whether one uses Docker. Scripting/automating this kind of thing may be a fixed cost initially, but even with a solo developer, it is likely to be very quickly amortized given the freedom to experiment.
- debarshri 5y agoOne development database kind of setup can also create conflicts while building and if the instance is small, it creates bottlenecks and decreases productivity.