Why this debate. SRE and DevOps have truly changed the way traditionally operations have been done. One thing all the prominent bloggers, tech leaders, and enthusiasts agree that SRE is not a glorified sysadmin. Read more here
However many companies often try to post job descriptions with really confusing titles and honestly I believe it is not their fault. Many in the tech community can't tell the difference either and many claim that they are one and the same. Google formally launched the term SRE and one of the articles here does a pretty good job of summarizing it. Here is another description by one of the guys who wrote google's famous book on SRE. You can read it here I believe many of us have also seen this video how Brian an SRE at Google talks about his experiences.
However, Many amazing people have written all about the long debate everyone is having.
The author of this blog says The whole summary I believe is what works for Google might not work for everyone else because contextually speaking every company's needs are different and what worked for Google might not work for them.
This one was pretty interesting and if you want its summary here you go..
Not every infrastructure needs an SRE, but every infrastructure could use an administrator who acted more like one. Instrumentation, scalability, repeatability…these are the watchwords of reliable infrastructures, and each one of us should work to improve them, and by doing so, improve our infrastructures.
The one I agree on with the most is one is again SRE and DevOps are quintessentially contextual and no matter what you call it DevOps or SRE. It is just about doing operations in a better way.
0 Comments