An SRE team deals with various domains of influence. I am outlining some of the ones that I find to be the most prelevant, in no particular order.
Sometimes an SRE organization may be known as the ‘no’ organization. This is really unfortunate. I would like to say that an SRE team is a ‘yes, if…’ organization. What I mean by that is, yes, you can push to production, if you have not exceeded your error budget.
SRE teams deal with a large cross section of infrastructure, such as analytics, notifications, validation, logging, monitoring, provisioning, storage and compute. Across all these functions, SRE’s have to be mindful of reliability, availability, scalability, automation, isolation, capacity planning and cost.