Monday, December 18, 2017

Why Database CI/CD?


Making the Database Part of Your Continuous Delivery Pipeline

The database, unlike other software code is not a collection of versioned files. Thus, Continuous Integration(CI) and Continuous Delivery(CD) for Database has taken a back seat to source code, leaving database automation to play a game of catch up at a high risk.


 In this analogy below, the conveyor belt represents Jenkins ( or such CI tools ) , the chocolates signify the application code releases / release cycle ( powered by CICD currently ) , and Lucy and Ethel are ‘handling’ the database code.








More to come..  :D 

Stay tuned!

--Debajit Kataki
at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

  Expand your network at ease : Six Degrees of Separation! PC: Psych2Go Did you know that you are just six connections away from any person ...

  • Why I decided To Write a Blog..
    Why I started blogging... Well, this is the ultimate question I get asked when I tell people I started a blog! I have taken a lot of time to...
  • Import Gmail Contact to my Outlook
    I worked with a start up employer where it happened that we got an email from out Top Boss! to block all google and yahoo cousins, to promot...
  • Trouble Uninstalling IE9?
    Just couple of days back I wrote a post on IE9 beta release . I saw it buggy and was wondering if some of you has problem uninstalling this ...