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

AWS re:Invent summary 2017

As you might know, this year’s AWS re:Invent was held @ Las Vegas 11/27 – 12/1.  

Below links could be a good start to explore all the new features and services announced at AWS re:Invent 2017

Product Announcements :  

https://aws.amazon.com/new/reinvent/

Categorised summary of news and analysis:  

http://searchaws.techtarget.com/conference/Your-guide-to-AWS-reInvent-2017-news-and-analysis

Links to YouTube recordings of AWS re:Invent 2017 sessions : 

https://gist.github.com/stevenringo/108922d042c4647f2e195a98e668108a

Hope this helps!