Continuous Delivery and the Development DBA

  • Comments posted to this topic are about the item Continuous Delivery and the Development DBA

    Pedro Lopez
    FIS

  • 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/.

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

  • 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

  • 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

  • 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!

  • 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

  • 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".
    "Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"

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

  • 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

  • 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.

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

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