Define class SRE implements DevOps

History

In the early software development, traditional waterfall model had been widely used for a long time.

From the experience, waterfall model may not help when the features need to be delivered in short.

As a result, agile development models are defined, the related tools and methods are made as well.

DevOps, is then grown up, leads closer collaboration between Development and Operation teams.

The culture or target, DevOps helps:

• Reduce the overhead on both Dev and Ops teams
• Speed up the software delivery time
• Better the service and value in business

Developers can use related tools or methods of DevOps CI/CD to simplify and automate the workflow.

However, how the operators afford the change from DevOps?

In Google, there is a team called “Site Reliability Engineering” which implements DevOps at Operation.

SRE overview

Historically, the sysadmins in Operation are keeping the services work properly.

However, when huge amount of servers needed to monitor and maintain, old way becomes clumsy.

Thanks to Infrastructure as Code of DevOps, treating operations as software becomes possible.

The target of SRE is to ensure the service-level agreement at high avalibility by automation.

The missions of SRE can be divided to three sections with priority.

1. Operation Automation: Develop automation tasks; Leverage different DevOps tools

2. System Administration: Allocate IT resources; Maintain the services; Handle changes

3. Emergency Response: Monitor the services with metrics and logs; Troubleshoot services’ issues