3 ms·
> SRE has an identity crisis. It means too many things to too many people. In some companies, it is an operational help desk. In a few companies, SRE is rumored
by dijit 4y ago
> SRE has an identity crisis. It means too many things to too many people. In some companies, it is an operational help desk. In a few companies, SRE is rumored to be a different aspect of software engineering.
SRE is Sysadmins but with better contracts between teams, and automation focused.
I haven't had much trouble with that definition, does away with all the cruft of the "Production" talk by Benjamin Treynor Sloss and the majority of the SRE books (which are a prescription of a method of creating those contracts).
That said: "DevOps" and Systems Administration in general has had an identity crisis for a while. People don't like the idea of "Sysadmin" for some unknown reason, but give the same role to someone and call them "DevOps" and suddenly all is well.
Same is now true of SRE.
Someone on HN said to me: "DevOps is how you get Engineering to respect Systems Administration".. Maybe the same is true of SRE?
I definitely feel the identity crisis of DevOps is much, much worse than that of SRE- but I guess that depends on your circles.
- kodah 4y ago> SRE is Sysadmins but with better contracts between teams, and automation focused. That's not even close to true, which I think is OPs point. For instance, I have an extensive SRE-SE background, but I'm also a software engineer. If I was tasked with "sysadmin" stuff, or shepherding peoples Jenkins jobs every day I'd probably lose my mind.
- Rapzid 4y agoSame, background in cloud/systems engineering, SRE, and staff full stack engineer. Or, FullStack++ as I sometimes like to call it haha.
- pojzon 4y agoHow do you call an Engineer that can do everything beside Frontend ?
- dijit 4y agoI think we misunderstand each other completely. There are many types of systems administrators; when we talk about as SRE in particular there some overlap with what I was doing as a “Linux Systems Administrator” in a Platform Engineering team, in 2009. Automating migrations, distributed job control, instrumenting the message queue system, managing cache invalidation across our entire fleet of memcache servers (which was ugly hacked with MySQL, not proud), as well as “maintenance” programs to upgrade “versions” (multi-tenant SaaS) and warm caches, dark launches, canary deployments… well you get the picture. Of course I was responsible for the reliability of the systems these things ran on, but there was a really-really strong focus on automation as part of the job, and this was when puppet was quite new, we were stuck with tools like cfengine. Coddling Jenkins sounds like build or release engineering. Which is also a separate thing. People seem to forget that systems administration has a focus on software development too- I mean for goodness sake terraform, ansible and salt all come from sysadmins; I suspect it’s because of some very foolish admins proudly exclaiming they don’t code. But they were always the bottom rung and end up being “promoted” to management at some point.
- kodah 4y agoI get more of what you're saying now, but I still think that reinforces OPs point because, to me, what you described is a Systems Engineer not a Systems Administrator. OP is asking for some structuring as to what these roles require in terms of knowledge. To me, "Administrator", "Engineer", "Technician", etc all prescribe different degrees of knowledge and also usually correlate with responsibility. As for "SRE" vs "DevOps" vs "Systems Engineer", I'm not so sure. For instance, I typically expect SREs to be able to write application software and orchestration software. I have similar expectations of someone who uses the title Systems Engineer but I might expect less application software development experience. DevOps I think I'd rather forget is a word.
- xorcist 4y agoSystems engineer is a title that seems to have fallen somewhat out of favor, but it wasn't unusual that it was a less hands-on role than sysadmin/SRE. Sometimes close to a system integrator but could also be what is now known as an infrastructure architect. Who do you think did the SRE work before that name was invented? Most likely it was your friendly sysadmin. It is the type of role that is not much noticed when done well, and probably that's why some feel it underappreciated enough to keep inventing new job titles. It's still the same job, pretty much the role that requires privileged access.
- nunez 4y agoReliability Engineering is much wider than the scope of a sysadmin. SREs are software engineers whose focus on the reliability of systems and platforms. Could be sysadmins; could be traditional SWEs; knowledge of both is required.
- apple4ever 4y agoNo they are the same thing. Reliability Engineering was always part of a sysadmin's job, but how much depended on the job.