A developers great journey into the world of Devops

So, in my organization, we use Red Hat OpenShift as a devops container to host our applications. So every time we push a new version into our git azure, the pipeline is automatically triggered to build the new image and deploy our application. The big advantage we got from using Red Hat OpenShift is that when we used traditional virtual machines to deploy our applications, we didn't know when the service stopped and every time the VM stopped, we had to restart the application (which is essentially a .jar file) again, it didn't restart automatically. In addition, the application artifact is created manually using maven commands. Fortunately, all this was solved using Red Hat OpenShift, because in Red Hat OpenShift we just push the code to git and the magic happens automatically.

In our old system, the developer starts developing the application then manually runs the unit tests and checks the results manually, downloads sonar to his local machine to check for bugs and code governance ... once he's done, he pushes his code to git then returns to his machine to manually clean and package the application and finally delivers the artifact to the operational agent who will connect the application to monitoring and logging tools like ELK and spring admin, eureka ... etc., once they have a change, they have to make sure that the latest version of the deployed code is the latest pushed version. and we're not forgetting the complexity of the procedure for creating a secure mesh service.Today, we use Red Hat OpenShift, so the developer simply pushes his code onto git, git automatically launches an Red Hat OpenShift pipeline (a custom pipeline that checks unit tests, code bugs, recoveries...), if the code is acceptable it is deployed, if not it sends an e-mail to the developer with a full report. And the mesh service is just one operator with a very small configuration. Red Hat OpenShift gitops gives us the power to manage the difference between the deployed image and the source code (if there is a difference between the two) and we're lucky enough to have a complete monitoring and logging dashboard.

as a financial institution, we need to always create a dev environment, a UAT environment and a PROD environment. Red Hat OpenShift gives us the opportunity to manage our 3 environments fluently specially that the DEV environment is an edge environment, it is only accessible by the coworkers, in the other hand, the PROD environment id a public cloud environment that can be accessible by all our collabs.