One of the aspects of DevOps, which is most important for developers, is automation, namely infrastructure as code. Utilization DevOps has button deployments that automatically create new windows, install all dependencies, download the application, and set all the appropriate configuration values. As with Test Driven Development when developing applications, there is a problem with DevOps for providing test deployments and writing tests to actually test that the software has been deployed and is working correctly.
DevOps also strives for a production application after its deployment. This is done by checking the application for monitoring and notification of errors. More than just this service works, but the service works well.
The other side of DevOps is related to business processes and more actively related to infrastructure and operations and removes these silos between operations, infrastructure and development. This affects developers because it eliminates "Jobs on my computer" or in the dev environment as a definition. It is executed that the application works and works as described in the userβs history or specification. Developers become more knowledgeable about the application in the production environment and more knowledgeable about the infrastructure.
It is still unclear where the DevOps borders exist, but the DevOps goal from the developer's point of view is to automate the infrastructure from deployments to configuration and, as such, to process the infrastructure as code in relation to verification of source control, verifiability, as well as automation, as well as tools for monitoring and notification.
Resources
Software
source share