Print

Electric Cloud releases DevOps solution



David Rubinstein
Email
July 18, 2012 —  (Page 2 of 3)
Keeping up with the workflow
The fact that ElectricDeploy is based on models helps provide a consistent way for all teams—development, QA, release and production—to follow a workflow process, Ramanathan emphasized. “If you want a consistent solution for all these teams, you cannot have an ad hoc way of doing things. What you need is a type model, and we do that in ElectricDeploy through three models. The first is an application model, which you typically define once, and that typically highlights the various components that make up an application: Web, application server, database, middleware, etc. It also speaks to the dependencies of these components; it speaks to the various configurations of these components, so now I can put my arms around what is the application.

“The next piece of the model is ‘where,’ and where essentially means the various environments where I’m going to deploy this application. The ability to model the infrastructure, the configurations of the infrastructure, the Apache Web Server, and the WebLogic/WebSphere app server, and the Oracle database servers or the VMs that may be involved in that environment, is very important. You will have many models depending on the number of environments you’re going to be deploying the application to.

“Finally there is the ‘how’ of the model, which is how do you marry the application to the environment, and that’s typically through a workflow process-execution engine, and we have the ability to very easily create these workflows in our product. So using these models—the what, the where, and the how—we are able to now automate the process of deploying an application to the various environments using the workflow model.”

Ramanathan said Electric Cloud sets itself apart by providing the ability to create what it calls a failsafe deployment. “The place where we really differentiate is by leveraging the fact that deployment happens many times through the release process, and to the extent we can iteratively refine the deploy process, we can capture errors in the deploy process early on, and we can fix these errors as we go through the process. And what it will ensure is, as you get to the final and most critical deployment that impacts the business, that will be as bulletproof as it possibly can be.”



Related Search Term(s): DevOps, Electric Cloud

Pages 1 2 3 


Share this link: http://sdt.bz/36804
 
Most Read  Latest News  Resources

close
NEXT ARTICLE
Open Cloud Initiative envisions an open cloud future
Vendor lock-in is a hidden danger, so principles must be established to protect users Read More...
 
 
 




News on Monday  more>>
Android Developer News  more>>
SharePoint Tech Report  more>>
Big Data TechReport  more>>

   
 
 

 


Download Current Issue
MAY 2013 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?