LOGIN | REGISTER NOW | SUBSCRIBE
 
Print

Guest View: Rise of the machines: Power brokers in DevOps bonding!


By Bola Rotibi
Email
July 1, 2010 —  (Page 1 of 5)
To some people, developers are ingenious innovative software generators. To others, they’re code hacking. Either way, the world they know is changing, and their role must evolve to take on more responsibility and be more accountable for the code and applications they create.

One of the more pressing challenges facing software development and delivery teams occurs when software is released and running in production. Deployment, release management and maintenance issues (especially in resolving problems once applications are working out in the field) are the bane of both the software production teams (the developers) and the operation teams alike. The problems are getting harder, not easier, with each technological and platform advance.

Knowing this hardship, you’d be hard pressed not to think that relationships between the developer and operations teams, called the DevOps bond, would be more in-tune to their respective requirements, shared challenges and goals, and be in general a lot more collaborative. Nothing can be further from the truth. The disconnect that exists between many development and operations teams is both legendary and ingrained.

The "throw it over the wall" attitude, a key culprit to the strained DevOps relationship, partly stems from the lack of deep and connected insight into deployed assets, process transactions and system configurations, as well as patches and management policies that exist in many production environments.

But, when all is said and done, the real culprit at the center of the breakdown in the DevOps relationship is a shameful disregard on both sides for the communication and connections that need to happen in order to understand the dynamics of an application deployed out in the field, and the impact of changes made either to the application or the field environment. A lack of knowledge and insight along with the failure to manage the expectations on both sides has resulted in time, money and other precious resources being wasted in resolving problems that arise. In truth, these are fundamental failings that underlie most of the woes of software development, delivery and the ongoing maintenance once an application or code component is deployed out in the field.



Related Search Term(s): professional development, virtualization

Pages 1 2 3 4 5 


Share this link: http://sdt.bz/34454
 
Most Read  Latest News  Resources
SAP unveils SAP HANA platform innovations for Big Data and spatial processing
Features include smart data access and expanded cloud deployment options
Alteryx raises $12 million to put Big Data analytics in the hands of all business analysts
Quest founder's firm, Toba Capital, selects Alteryx as its first analytics investment
Google I/O kicks off
Developers get new APIs and tools, and the Go language hits version 1.1
Jelastic launches new version of its Java and PHP hosting platform
Jelastic today announced the launch of a new version of its ultra-scalable cloud hosting platform
Digg!  Digg
Reddit  Reddit
Slashdot  Slashdot
Share on facebook  Facebook
Share on Twitter  Twitter



Comments


07/04/2010 05:23:04 AM EST

Great and informative article, especially the need to application service automation. Nolio ASAP is a platform just for this, that knows how to take complex and multi tier application deployment processes, and model them in an easy to use interface that can get executed in development, QA, and production. Available at http://www.noliosoft.com

United StatesDaniel Kushner


07/08/2010 01:37:07 PM EST

Very insightful article. Especially agree with the point that developers should take more responsibility for helping operations. It makes sense since they are the ones who know application architecture and deployment environment best. One of the key issues there is providing continuous monitoring of applications and their relationships to resources - services, hardware, middleware, storage, etc. The more thought is given to the metrics that represent health and performance of the applications, the more empowered operations are in productions. IntegraSolv's OWL is just such as product. It allows developers to communicate performance and relationships to operations personnel using application instrumentation. Whether components are running in the enterprise, in the cloud, or in a mixed environment, Owl represents a valid, application focused picture. Available at http://www.integrasolv.com

United StatesArthur Frankstein


close
NEXT ARTICLE
Third-party tools showcased at Professional Developers Conference
ComponentOne has a new development kit for the iPhone and the iPod Touch, while Infragistics created a version of NetAdvantage for Silverlight. Also, Developer Express and Microsoft announced a joint code-quality effort for C# 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?