Continuous Delivery and the Development DBA

Question

Continuous Delivery and the Development DBA

pedrolopezmail

SSC-Addicted

Points: 480
More actions
March 21, 2017 at 10:21 pm

#335834

Comments posted to this topic are about the item Continuous Delivery and the Development DBA
Pedro Lopez
FIS

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

andrew.whettam SSC Enthusiast Points: 194 More actions · Answer 1

Thank you Pedro, a useful and informative article. The sections on the Abstraction, Expand and Contract, and Feature Toggles patterns are particularly interesting. I am, however, surprised by your statement: "Trunk-Based development is the recommended branching strategy for Continuous Delivery". There are many expert software teams using branching as a core component of their CI/CD strategy. Indeed, in some situations branching is a necessary approach to avoid such anti-patterns as code freezes. One example of a branching strategy which is recommended by some ALM practitioners (e.g. Marcel de Vries) is Vincent Driessen's 'A successful Git branching model', which can be found here: http://nvie.com/posts/a-successful-git-branching-model/.

corey cummings SSC Journeyman Points: 87 More actions · Answer 2

There is a typo in the refactored code "ALTER PROCEDURE dbo.Get_UserDetails( @userid INT)", the where statement should use @userid

pedrolopezmail SSC-Addicted Points: 480 More actions · Answer 3

corey cummings - Wednesday, March 22, 2017 6:32 AM
There is a typo in the refactored code "ALTER PROCEDURE dbo.Get_UserDetails( @userid INT)", the where statement should use @userid

Hi Corey

You are correct. but technically it can be call a bug. 😉

thank you.

Pedro Lopez
FIS

pedrolopezmail SSC-Addicted Points: 480 More actions · Answer 4

andrew.whettam - Wednesday, March 22, 2017 3:57 AM
Thank you Pedro, a useful and informative article. The sections on the Abstraction, Expand and Contract, and Feature Toggles patterns are particularly interesting. I am, however, surprised by your statement: "Trunk-Based development is the recommended branching strategy for Continuous Delivery". There are many expert software teams using branching as a core component of their CI/CD strategy. Indeed, in some situations branching is a necessary approach to avoid such anti-patterns as code freezes. One example of a branching strategy which is recommended by some ALM practitioners (e.g. Marcel de Vries) is Vincent Driessen's 'A successful Git branching model', which can be found here: http://nvie.com/posts/a-successful-git-branching-model/.

Hi Andrew

thank you for reading. I have no doubts that GIT works, but for large team 100+ member ( 15+ teams). The overhead of merging is to big. It is recommended trunk-based development and extensive automated integration testing.

Pedro Lopez
FIS

Andy Warren SSC Guru Points: 119902 More actions · Answer 5

Pedro, I use branching and find it to be a reasonable approach for our environment. Do you think trunking is critical. To me it feels overly prescriptive. Enjoyed the overview of patterns!

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter

pedrolopezmail SSC-Addicted Points: 480 More actions · Answer 6

Hi Andy
I have no doubt that the right team, regardless of the branching strategy will succeed. Trunk-based development is highly recommended for large teams while doing continuous delivery. However, It is not the only option. Based on Martin Fowler and Jez Humble's experience (as expressed in the Book "Continuous Delivery") trunking is recommended. I'm glad you enjoyed the reading of development patterns.
Thank you.

Pedro Lopez
FIS

Jeff Moden SSC Guru Points: 1003853 More actions · Answer 7

Nothing to do with the article... I'm just really happy that I don't work for a company with 15 development teams and 100+ developers. 😉

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

pedrolopezmail SSC-Addicted Points: 480 More actions · Answer 8

Hi Jeff,
You are right, it is challenging at times and most of the time not in a technical way. 🙁
Thank you.

Pedro Lopez
FIS

Yet Another DBA SSCarpal Tunnel Points: 4299 More actions · Answer 9

Instead of dbo.Get_UserDetails create a new sproc dbo.Get_UserDetailsByName ...

Changing the contract/signature which seems to be the suggested route is not recommended by sOlid principles or by many experienced C# developers. Yet, it seems that when it comes to the database world we throw out a lot if good practice that has been discovered & evolved by out counterparts who do more coding then us.