Operations was unloved. In the world of software application development and enterprise technology management, no system runs reliably without a solid engineering support function and service layer – in most cases we call that entity the operations team.<\/p>\n
As the Ops in DevOps (the portmanteau joining of Dev-developers and Ops-operations teams in one unified work ethic methodology to promote workflow harmony and encourage a more equitable unified approach to running enterprise technologies so that we all get apps that work), the operations function has been previously looked down upon by professional developers (hence much of the reason for DevOps in the first place) who sometimes view the IT \u2018service mechanics\u2019 that work in this division as people who couldn\u2019t cut it at the coalface of hard coding and programming logic.<\/p>\n
Operations has enjoyed a vibrant renaissance throughout the post-millennial era of cloud computing, probably because this model of computing is so inherently based upon service provision. The applications are still important, more important than ever in fact, but the need to underpin them with a services structure that is ever-present, always-on and resilient in the face of user demands for scale, enhancements and change is now paramount. Let\u2019s tour the 17 types of Ops with a contextual definition.<\/p>\n