The first question that should pop out of the mind of an inquisitive learner is "what in the world is DevOps?". Perhaps the first place to begin is what DevOps is not. DevOps is not a programming language, it is not a tool, a framework, a library, a utility class, or all the other terminologies around and within programming. Then let's come to what DevOps is, DevOps is the little drops of water that make a mighty ocean philosophy, ethics, or culture in software development. It is a way of shrinking the long period of time needed to develop a product due to the back-to-back interchange and confusion between the development team and the operation team. From the ongoing, two teams are involved. First, are the development teams (DEV) which are in charge of coding, building, and testing, and the Operations team(OPs) in charge of deployment, server management, and scalability. These two teams make up DevOps. Prior to now, both teams work in silos and there was a middle wall of partition between them, they pass messages through tiny windows, with no proper communication, which in turn made developmental processes long. But all hail DevOps, it merges the two together and made it possible for the two teams to communicate better, deliver products in batches or in sprints, and for members to work on both ends. Sincerely, DevOps is the agile software development pattern. Conclusively, we could say DevOps is the amalgamation of development and operations teams to continually work together to deliver products continually without the usual time lag.
Look forward to Day 2.