By John L Myers
Automation can be a huge help, but automating concepts before you understand them is a recipe for disaster. The concept of devops has taken root in the world of business intelligence and analytics.
The concept of devops has taken root in the world of business intelligence and analytics.
The overall concept of devops has been around for a while in traditional IT departments as they sought to expand and refine the way that they implemented software and applications. The core of devops in the world of analytics is called DWA (data warehouse automation), which links together the design and implementation of analytical environments into repeatable processes and should lead to increased data warehouse and data mart quality, as well as decreased time to implement those environments.
Unfortunately, for several reasons the concept of data warehouse automation is not a silver bullet when it comes to the implementation of analytical environments.
One reason is that you really shouldn’t automate concepts before you fully understand them. As the saying goes, don’t put your problems on roller skates. Automating a broken process only means that you make mistakes faster. Now, while I often advocate the concept of failing faster to find the best solution to an analytical problem, I don’t really agree with the concept of provisioning flawed database structures very quickly only to rebuild them later.
Read more at Info World