5 Things to Know about CICS and DevOps
MartinKeen 1200007VU3 Visits (9496)
The world of software development has been changing for some time. The advent of more devices, such as tablets and mobile phones that need to run software for larger audiences has created a different style of software development. In order to compete at a much larger scale, companies have been forced to review their software development and deployment processes to decrease time to market while increasing reliability, thereby reducing time to fix problems that are inevitable in software development. That is when the concept of Deve
1. Merging Development and Operations into DevOps
The process of plan -> develop -> build -> deploy -> feedback is continuous. When possible, human actions are minimized in favor of autonomous tools, including software builds that kick off automatically when eligible code updates become available. Applications reach their full potential faster, often using fewer resources.
By developing small incremental changes rather than large releases innovative features can be deployed quickly allowing users to market test these features before continuing down certain paths. This process becomes repeatable and ongoing leading to much more agile development. The quicker feedback, and smaller changes results in improved time to market.
These tools also quickly integrate with products such as Rational Developer for System z (RDz) and Rational Team Concert making the DevOps strategy a reality for the development of CICS based applications.
The key to faster deployment relies on the automation of the build and deployment processes. As these processes will be done more often in the DevOps style of software development, the automation will remove the human errors that can occur, leading to a repeatable process. This in turn leads to a continuous integration practice where developers deliver code in chunks providing more frequent releases of software.
The automation of the build and deploy process also allows management to cope with the increasing complexity of release management in an environment where the time to build and deploy occurs at a rapid pace. All the while not sacrificing the flexibility, reliability and re-usability that continuous delivery and deployment requires.
Since the coding changes are occurring more frequently the amount of change that needs to be tested will be much smaller. This will allow the testers and customers the ability to provide feedback quickly resulting in rapid fixes or additional features. This will greatly enhance the time to market.