re: How you guys handle database versioning? VIEW POST


For a situation like yours, the only method I've found that works well is to use a dedicated DBA who acts as a chokepoint that all the developers have to use. They oversee any changes to the schema, review and optimize queries, deal with master/slave/follower scaling challenges, and handle versioning with roll-forward and roll-back between releases. On a big enough team, they will be very busy. The bit is dedicated DBA roles have fallen out of fashion, but they are very helpful on large projects.

code of conduct - report abuse