What really is DevOps?
A definition of DevOps with examples, from the perspective of feedback loops.
This article talks about the magic of DevOps, what it represents and what benefits it brings. Every organization usually has its own definition of DevOps. That is why I try to present it as a general definition with examples so that even us ordinary people can finally understand what it means.
Some people define DevOps as a cultural movement, others as a set of tools. I think it both at the same time. However, I would put more importance on culture, as it can make systems work really effectively, even without the latest tools.
Let us switch the context a little and think about animals. Animals right? Why am I reading this? … Stay with me.
Imagine a tiger, yeah just like the one in the picture. When a tiger is very hungry he is really focused and senses every change in his environment to achieve his goal of getting food. When he senses that there are other animals in his vicinity that he could eat, he can very quickly respond to that information and act on it. He can start hunting very quickly and catch that poor zebra. If his feedback loops are fast and he can act on the change quickly, he can be a very successful hunter, which will benefit his whole family of tigers. For the zebra that is not such good news, unfortunately.
Feedback loops, generally, are very important in life and different systems as they define flexibility. How flexible a system can be, is usually very correlated to long-term success. If we think of a business that can not adapt quickly to change like for example Kodak did not adapt to the mainstream use of digital cameras and therefore deteriorated from a very successful business to a failing one.
If you can make your system (usually an architecture of code, infrastructure and/or services) be very responsive to the environment (users needs, bugs, market changes…) and to the changing internal properties of the system (inclusion of new technologies, changes of architecture…), the system can be very successful and efficient.
I think about DevOps from a perspective of feedback loops. If you can implement fast feedback loops in your system, as described, it will bring a lot of business and technological benefits to your organization.
If you read my thoughts, I congratulate you. I have probably disappointed you, no technical description was really provided, but this is a perspective I want you to think about. I will provide a more technical and detailed description in a later article that will work with this perspective.