If not, you should probably consider it.
Organisations that are using DevOps are seeing significant improvements in the performance of their IT organisation, in areas such as:
● time to market
● failure rate
● time to recover from failure
This improved IT performance is reflected in better business performance. Companies with high - performing IT saw 50% higher growth of their market capitalisation over three years compared to those with low or medium performance IT functions.
So what is DevOps? Fundamentally it is a culture. One in which development and operations work together rather than in opposition. This might sound like an obvious thing to do. However development and operations have traditionally been organised in a way that promotes conflict, rather than collaboration.
Traditionally, development is focused on innovation, operations on stability.
Development creates new software, or modifies existing software. For development change means progress.
Operations works to satisfy SLAs - keeping systems available and performing. For operations, change means risk.
Since the two groups basic goals are in opposition, it is no surprise that the relationship between them has typically been characterised by conflict.
DevOps replaces this culture of conflict with one of collaboration. Both teams share the same goal, and are equally accountable.
A useful analogy here is a factory production line. All of the stages of the process have to be completed successfully before a product can be considered “built”. By focussing on the end goal, all of the teams work together.
Like industrial manufacturing, a key enabler for a DevOps approach is automation. In particular the automation includes the provisioning and configuration of runtime environments. The scripts used to achieve this are considered part of the overall build (“infrastructure as code”), and are included in source control.
The use of automation dramatically reduces the time taken to deploy code changes, whether to production or test environments. This means we can deploy “little and often” - going faster, but with less risk.
While DevOps does not require use of cloud as a deployment platform, the ability to rapidly provision and configure environments via automated tooling is a characteristic of a cloud platform. So cloud is a natural choice of platform for DevOps.
The Oracle Cloud platform has been engineered to help Oracle customers adopt or extend the use of DevOps.
At the heart is the Oracle Developer Cloud Service. This provides enabling capabilities to support a DevOps approach:
● Git code repository for source control
● Code review
● IDE integration (OEPE, NetBeans, JDeveloper)
● Issue tracking
● Continuous Integration using Hudson
● Deployment (automatic or on - demand)
In a typical scenario, a developer would make code changes and then push these to Git. Hudson would detect that code had changed and run a build job or jobs to build the application and run unit tests. The application would then be deployed into the target environment.
Operations staff could then monitor the application in the target environment and raise issues or requests for further improvements in the developer cloud service for the development team.
Oracle Developer Cloud Service is included with the following Oracle Cloud services:
● Java Cloud Service
● Java Cloud Service - SaaS Extension
● Messaging Cloud Service
Unfortunately we can’t change your organisation to a DevOps culture for you, but we can enable that change if you choose to embrace DevOps.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.