I’ve been attempting to expand my reach to get back to my roots in development. I’m doing this because I really believe in the concepts behind devops, that these walls we’ve erected between development and dba, between dba and san admin, et, ad nauseum, cetera, need to come to an end. The great news is that there are a lot of other people who feel the same. We’re changing things. Come on over to the dark side, we have wine. Any way, I had a blast talking database devops with Bryan for his podcast. Have a listen and let me know what you think.
I just listened to your podcast on Devoops and thought “right on”. One thing that no one talks about is the issue of bad design showing up in the db. So how do you address that in the rapid deployment world…I not talking simple stuff either but tables that have repeating columns1,2,3, lookup values imbedded in columns as text., other stuff when you say we need to change some of this the answer is, “it’s already coded and tested no time to redo…the sprint is over tomorrow.
Great question. The answer… well, it’s hard. The main thing I advocate for, and have been occasionally successful doing (and some failures) is for the dev team to have a database person, either a DBA or a database developer involved right from the start of the dev process. Fixing problems at the start is easy. You can’t fix it on deployment day, ever.