💚 Check out: "What is DevOps" video ► th-cam.com/video/0yWAtQ6wYNM/w-d-xo.html 🧡 Get notified about new upcoming courses ► www.techworld-with-nana.com/course-roadmap 💛 Follow me on IG for behind-the-scenes-content ► bit.ly/2F3LXYJ 💙 Become a DevOps Engineer - full educational program ► bit.ly/3ICgXwJ ▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬ 0:00 - Intro and Overview 01:09 - Why was there a need for SRE? 02:19 - What is SRE? - Official Definition 03:13 - What is system reliability and why it's important? 05:20 - How to make systems reliable? 09:07 - SRE in Practice: SLA & Error Budget 14:01 - SRE Tasks and Responsibilities 19:41 - Who is doing SRE? SRE Role 21:06 - SRE vs DevOps
As a long time Software Engineer who moved into a DevOps Engineer role and now into an SRE role , Nana explained the differences of a DevOps Engineer and SRE very well. Good job!
Thank you Nana - After watching your videos as a software engineer for over two years I have just been offered my first job as a DevOps engineer at a startup. Many thanks!
I have worked both as a DevOps and SRE. Your explanation to both concepts and roles is on point. I personally prefer the DevOps role and I will be transitioning back to it. I enjoy more working in the Infrastructure as Code side, involved with CI/CD and Cloud tools. My Experience as an SRE was more related to monitoring and incident handling, which is sometimes a pain in the a**. Greetings from Colombia!
As an ex SRE and now DevOps engineer and in my opinion, no one really care what is the difference. I know only one company where the tasks of SRE and DevOps are different. For companies which are just steped into cloud computing (and not only those) both the DevOps and SRE are the fency words and describes the same System Administrator, who takes care about the infrastructure, able to solve their problems and restart appropriate service in the middle of the night. Why I'm writing this? Just to ask you, please, next time when you will get a message on Linkedin from recruiter who will say "hay, we have a cool DevOps position where you will need to be on-call and do some monitoring tasks" say him/her "but this is not a DevOps role. It sounds more SRE".
Great video! As an SRE at a big tech company, we do things a bit different than the well-known SRE concept mentioned in this video. We have dedicated tools teams filled with SWEs working on building the entire CI/CD platform and on-prem resource allocation. We also have dedicated netops, sysops teams working on networks, hosts, file-systems, etc. For SREs, we do the typical work like monitoring, oncall, automate dashboard generation, but the real fun stuffs are building technologies that help make the site more reliable and fast. Some examples are, we built our own monitoring platform, end-device availability observations, ML-powered incident triaging/mitigating, ML-powered service performance tuning, database data integrity detection/restoration, etc. All of the projects mentioned above help make the site more reliable but not necessary focusing on making feature delivery fast.
As a SRE we are setting, 1. we will collect metrics of different servers and displaying on Grafana dashboard ,2. operational alerts to respective teams. 3. ONCALL on P1/P2 incidents. 4. Submitting the RCA to clients 5. working on the Incident action items with the developement teams.
Great video. We're currently in the process of budding off from the platform engineering team (I still can't bring myself to say DevOps team) to start a dedicated SRE function. This video illustrates so much the direction I want to take the team, but with some differences as we're currently a very small team servicing a large number of developers. So taking a more horizontal / consultancy type approach. So some challenges there... But I am definitely going to share this video as it really gives a great introduction into much of what we want to achieve. Thank you.
You have such a great way of explaining concepts like this. I've worked as a "DevOps" since 2003 - back then I was just a "build manager" and more recently am SRE at a big retailer. I don't think I really thought there was a difference and I'm not sure where I work that they think this way. You asked what would be great courses or videos - I'd love to hear more about infrastructure as code, configuration as code and best practices with tools like Terraform, Ansible, Chef/Puppet, Morpheus or even Jenkins/GitLab to run these "playbooks"
Hey NANA Loved the video as always. Just one suggestion, whenever your add started please add promotion alert or their logo in your video, it will help to differentiate the add and your content. In current loft promotion, after 10sec it feels it has ended but still it was going on.
bhaiji aapke jaise logon ki vajah se hi hum indians ki beijatti hoti hai. Har sponser chaahta hai k uske ad ko viewer neglect na ker paaye and that is what she is trying to do or aap us per lecture de rahe ho.
Hello Nana! Great Video as always. I owe my entire DevOps Journey to you. From becoming a complete Noob to now Working Full Time as a DevOps Engineer, You are my saviour. I'm now trying to transition to SRE. Can you help me understand what Tools should I learn for this? Also a Zero to Hero on SRE would be absolutely wonderful ! Anyways Thanks for Everything !!!
Super informative as always nana. - thank you i take away a few things from this and probably wrong: 1. Job postings i look at, seem to get DevOps and SRE confused or at least blend the two together it would seem...judging by the tool set/overall goals the two disciplines aim for... 2. Wouldn't surprise me if in the future, smaller companies start demanding more and blend both DevOps and SRE discipline together to save money (given that there is some overlap in concepts/goals): DRE (Development Reliability Engineer) or SRO (Site Reliability Operative/tions) :)
i think something missing here is the concept of "reducing toil." SRE have a lot of manual tasks. The team should look towards automation through both tooling and creating new applications that can do activities for SRE team.
Good explanation however I would like to address your story about SLA & Error budget. SLA is an agreement as you explained, but you mention it's set by the business owner and engineering, typically that won't be the case. After breaching an SLA there is most of the time in the contract a line that would allow the customer some form of reimbursement (money back, opting out of the contract). Most of the story telling is actually about SLO's, which are objectives that are set by the people who own the service (from Product manager, Product Owner and engineering team). This is where the story of Error Budget makes much more sense. You will never go close to your SLA because that would put a high risk of reimbursement. In short and SLO might have the same metrics as an SLA however a SLO should always aim higher then an SLO, because then you are (as you mention) allowed to take risks from your error budget. But also you might have SLO's (let's let latency) that are at the start not an SLA, but after a period you can confidently add that latency as an extra agreement with your customers without making assumptions. This is where the power of history data comes in play. SLO/SLI and Error budgets require it's own video, it's so powerful if you connect the dots, it's for me key metrics that can be understood by everyone in the organisation.
Hey Lee, thanks for sharing with great details! I agree that this topic requires its own video, I didn't want to explain all the details in this SRE overview video
@@TechWorldwithNana I believe you touched on the important items and made it clear what the differences were so kudos for again explaining to a broader audience. Also agree with your point, SRE can go pretty broad in topics. I am btw (because you asked in your video) a SRE Lead/Manager.
Thanks Lee for your feedback and for sharing your valuable knowledge as an SRE lead here in the comments with others as well. There is definitely a need for more information on these topics in the community.
Good video. I think what you explained as SLA is actually SLO. SLA is more of a commercial agreement that specifies kind of fine when you fail to meet SLO. You also missed one very important topic which is SLI.
I'm a second year computer science student and this is the very first time I've ever heard of such a role named site reliability engineer. I guess there's still a lot to learn. Great video though❤❤
As an SRE I like building and setting up the tools. For example writing scripts that detect changes and alert based on those incidents. But actually handling those incident is a pain in the ass because it involves a lot of communication with other people, emails etc
One of the best thorough and comprehensive explanations of SRE, or I must say, THE BEST! I love the comparison part between SRE and DevOps so much! Thank you for your work and knowledge, Nana!!
When you explain SLA you are really talking about SLO. The SLA is an agreement with some kind of consequences, usually financial. SLO is the objective that defines the availability, as an example, and the SLIs are the indicators you measure it with.
Great videos! Also watched the DevOps one, I especially appreciate how you address the ambiguities. My 2 cents on DevOps and SRE: are they almost the new Dev & Ops, but an upgraded version where both sides now need to have a broader knowledge of the full software life cycle. At the end of the day, each side still have their priorities (speed or reliability) as you can't really ask people to care about everything.
I thought SRE was a made up role when I was offered the position at my company. Whew, little did I know. I'm 2 months into it and this little software dev / software QA automator is swimming in a firehose of education. So much new to learn.
interesting to see the difference between practical devops and sre. we have a team of devops engineers, but you can see who acts more according to the sre or practical devops roles.
I recently transitioned from an information systems engineer to an SRE. Our current company’s goal for this role is to create a CI/CD pipeline, since it does not exist yet. However, we want to be able to monitor and keep our systems up and reliable moving forward.
So, to summarize, in the past we had two teams with different objectives: Devs for speed, Ops for reliability. And now we have 2 teams with "different" objectives: SRE for reliability and observability and DevOps for speed in releases and infra provisioning. Nice 🙂👍
I don't agree with that statement. SRE cares about reliability and observability, they can be either included in teams or act as a consultant to the different teams. They mainly drive improvements forward and will help the teams achieve that next level on topics like reliability/scalability/performance/observability. In regards to your DevOps team, in a "you build it you run it" way, the teams will take the tasks of deployment and infra provisioning on themselves because they have all the know-how of the application. Unfortunately in many bigger/older companies, this is not true and you have siloed teams (dev/infra/qa...). Note: I don't like the term DevOps team, it's a philosophy and not a role.
@@azzy6543 For me that's indeed a platform team, not SRE. However many teams in the organisation can help and mature reliability within their team without being called SRE. However I would not consider the platform team to be true SRE's as they might have not enough influence on the application code itself.
Overall, a good video. However, your explanation of SRE's role is around logging, monitoring and alerting. I thought I heard you say SRE's role is also to ensure what impacts new changes will have on the reliable and that this is through automation. And that this enables developers to push code more frequently. Other than the mention, I didnt hear how SRE does that. Specifically what are they automating to ensure new changes wont affect the site reliability. Is there more to an SRE other than logging, monitoring, alerting and post mortem?
The last segment is the best. I've been an SRE for 6 years or so now and never really noticed that we flip-flopped "personalities". In the 200X's ops wanted to slow the releases, congrol changes, etc. to keep things stable, while developers wanted to crank out chnages quickly with no care to stability. Fast forward to today and we've flipped. Now, the SRE (developers) want to focus on reliability while DevOps (Ops) want to crank up the speed of releases.
Thanks @nana for sharing this video, Great game, as usual :-) I would like to challenge a little bit the sillos we are trying to create between DevOps ( Build ) and SRE ( Run ) . A DevOps Engineer should not focus only on speed, but also on quality , as you mention in your video. SRE is a critical task to ensure we deliver with quality, and is part of the so valuable feedback loop of DevOps. In case the team size grows, once could isolate the roles within a team, but I would rather recommend to keep these people in the same team and exchange the roles in a monthly basis, so they can share the same goal and manage their skills accordingly. Side question: SLA is a key metric to monitor, but I usually found people building their own in house grafana dashboard to observe and alert. Any counter proposal to harmonize this asset?
Very well explained.... I had a few gaps in understanding how SRE is different from DevOps ... your video covered all those gaps ... thanks a lot Nana for the wonderful explanation !!!!!
Thanks for the video. I'm working as SRE currently, I think, besides the monitoring and alerting tasks, we also have response to incidents - PRODUCTION tasks which "DEVOPS" doesn't do.
💚 Check out: "What is DevOps" video ► th-cam.com/video/0yWAtQ6wYNM/w-d-xo.html
🧡 Get notified about new upcoming courses ► www.techworld-with-nana.com/course-roadmap
💛 Follow me on IG for behind-the-scenes-content ► bit.ly/2F3LXYJ
💙 Become a DevOps Engineer - full educational program ► bit.ly/3ICgXwJ
▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬
0:00 - Intro and Overview
01:09 - Why was there a need for SRE?
02:19 - What is SRE? - Official Definition
03:13 - What is system reliability and why it's important?
05:20 - How to make systems reliable?
09:07 - SRE in Practice: SLA & Error Budget
14:01 - SRE Tasks and Responsibilities
19:41 - Who is doing SRE? SRE Role
21:06 - SRE vs DevOps
Great video Nana ... What tools do you use for your presentation? Where do you get the artworks?
0:15 years
As a long time Software Engineer who moved into a DevOps Engineer role and now into an SRE role , Nana explained the differences of a DevOps Engineer and SRE very well. Good job!
I am seeing pattern of SDE moving into an SRE role more and more nowadays, can you explain your reasonings behind it? Thanks!
@@Jumboplaya💰💵💵💲💶💴💷
Thank you Nana - After watching your videos as a software engineer for over two years I have just been offered my first job as a DevOps engineer at a startup. Many thanks!
hii Gregg, could you please help me learn DevOps, any resources, any roadmap, please help me. thank you
Wow, that's amazing! Happy my videos could help you in your transition to DevOps :) Thanks for sharing!
I have worked both as a DevOps and SRE. Your explanation to both concepts and roles is on point. I personally prefer the DevOps role and I will be transitioning back to it. I enjoy more working in the Infrastructure as Code side, involved with CI/CD and Cloud tools. My Experience as an SRE was more related to monitoring and incident handling, which is sometimes a pain in the a**.
Greetings from Colombia!
thanks! it helps me understand both sides of coin 🤝
So are you saying DevOps roles are more enjoyable than SRE in general? Why?
Do anyone know what the is the team name that SREs are under?
@@zltdamdam I think that's subjective
@@pramilaaranvoyalrajan3361 Mainly PSS team or Prod support team
I am an SRE myself and the whole video is Spectacular way of explaining what SRE is. Great work!
As an ex SRE and now DevOps engineer and in my opinion, no one really care what is the difference. I know only one company where the tasks of SRE and DevOps are different. For companies which are just steped into cloud computing (and not only those) both the DevOps and SRE are the fency words and describes the same System Administrator, who takes care about the infrastructure, able to solve their problems and restart appropriate service in the middle of the night. Why I'm writing this? Just to ask you, please, next time when you will get a message on Linkedin from recruiter who will say "hay, we have a cool DevOps position where you will need to be on-call and do some monitoring tasks" say him/her "but this is not a DevOps role. It sounds more SRE".
Great video!
As an SRE at a big tech company, we do things a bit different than the well-known SRE concept mentioned in this video. We have dedicated tools teams filled with SWEs working on building the entire CI/CD platform and on-prem resource allocation. We also have dedicated netops, sysops teams working on networks, hosts, file-systems, etc. For SREs, we do the typical work like monitoring, oncall, automate dashboard generation, but the real fun stuffs are building technologies that help make the site more reliable and fast. Some examples are, we built our own monitoring platform, end-device availability observations, ML-powered incident triaging/mitigating, ML-powered service performance tuning, database data integrity detection/restoration, etc. All of the projects mentioned above help make the site more reliable but not necessary focusing on making feature delivery fast.
Awesome! This is actually a field I'm highly interested in if you don't mind what steps would you take to get into SRE
Whoa!!!! I was just thinking to know more about SRE and this video notification came 🤯🤯
Cool :D
As a SRE we are setting, 1. we will collect metrics of different servers and displaying on Grafana dashboard ,2. operational alerts to respective teams. 3. ONCALL on P1/P2 incidents. 4. Submitting the RCA to clients 5. working on the Incident action items with the developement teams.
is SRE Production Support?
@@RK-xg3qpyes
Great video. We're currently in the process of budding off from the platform engineering team (I still can't bring myself to say DevOps team) to start a dedicated SRE function. This video illustrates so much the direction I want to take the team, but with some differences as we're currently a very small team servicing a large number of developers. So taking a more horizontal / consultancy type approach. So some challenges there... But I am definitely going to share this video as it really gives a great introduction into much of what we want to achieve. Thank you.
I was just in a similar situation as well. Have you been able to achieve your ideal operational efficiency?
Thank you sister. This has made my day. Now I fully understand the differences between SRE and DevOps. God bless ya
This is the best presentation I have seen on the subject: clear, on spot, complete. Thanks!
Great video Nana! As an SRE, this is one of the best explanations I've seen!
Thank you so much, great to hear that from an SRE practitioner! :)
@@TechWorldwithNana thank you for the video, i learnt quite a lot when embarking on a new role as devops
Right in time! Just spending my first week as a junior SRE (but experienced sysadmin). 😃
Great to hear! Good luck with your new position 😊
You have such a great way of explaining concepts like this.
I've worked as a "DevOps" since 2003 - back then I was just a "build manager" and more recently am SRE at a big retailer.
I don't think I really thought there was a difference and I'm not sure where I work that they think this way.
You asked what would be great courses or videos - I'd love to hear more about infrastructure as code, configuration as code and best practices with tools like Terraform, Ansible, Chef/Puppet, Morpheus or even Jenkins/GitLab to run these "playbooks"
I am an SRE and my pain portrayed as a poem in this video. #respect
Refer me bro
Hey NANA Loved the video as always. Just one suggestion, whenever your add started please add promotion alert or their logo in your video, it will help to differentiate the add and your content. In current loft promotion, after 10sec it feels it has ended but still it was going on.
bhaiji aapke jaise logon ki vajah se hi hum indians ki beijatti hoti hai. Har sponser chaahta hai k uske ad ko viewer neglect na ker paaye and that is what she is trying to do or aap us per lecture de rahe ho.
Hello Nana! Great Video as always. I owe my entire DevOps Journey to you. From becoming a complete Noob to now Working Full Time as a DevOps Engineer, You are my saviour. I'm now trying to transition to SRE. Can you help me understand what Tools should I learn for this? Also a Zero to Hero on SRE would be absolutely wonderful ! Anyways Thanks for Everything !!!
Super informative as always nana. - thank you i take away a few things from this and probably wrong:
1. Job postings i look at, seem to get DevOps and SRE confused or at least blend the two together it would seem...judging by the tool set/overall goals the two disciplines aim for...
2. Wouldn't surprise me if in the future, smaller companies start demanding more and blend both DevOps and SRE discipline together to save money (given that there is some overlap in concepts/goals): DRE (Development Reliability Engineer) or SRO (Site Reliability Operative/tions) :)
Thank you so much.. I do all these stuff everyday but this video helped me to explain to someone what I do everyday..
Thank you nana!! I was waiting for this specific video!
i think something missing here is the concept of "reducing toil." SRE have a lot of manual tasks. The team should look towards automation through both tooling and creating new applications that can do activities for SRE team.
Very keenly explained, am an SRE we do all the things she mentioned.. good video!
I love your teaching Nana. Even a kid will understand your calm voice ❤
Thank you for your videos! I will be starting my new job as an SRE on monday jumping from it support
Good explanation however I would like to address your story about SLA & Error budget.
SLA is an agreement as you explained, but you mention it's set by the business owner and engineering, typically that won't be the case. After breaching an SLA there is most of the time in the contract a line that would allow the customer some form of reimbursement (money back, opting out of the contract).
Most of the story telling is actually about SLO's, which are objectives that are set by the people who own the service (from Product manager, Product Owner and engineering team). This is where the story of Error Budget makes much more sense. You will never go close to your SLA because that would put a high risk of reimbursement.
In short and SLO might have the same metrics as an SLA however a SLO should always aim higher then an SLO, because then you are (as you mention) allowed to take risks from your error budget.
But also you might have SLO's (let's let latency) that are at the start not an SLA, but after a period you can confidently add that latency as an extra agreement with your customers without making assumptions. This is where the power of history data comes in play.
SLO/SLI and Error budgets require it's own video, it's so powerful if you connect the dots, it's for me key metrics that can be understood by everyone in the organisation.
Hey Lee, thanks for sharing with great details! I agree that this topic requires its own video, I didn't want to explain all the details in this SRE overview video
@@TechWorldwithNana I believe you touched on the important items and made it clear what the differences were so kudos for again explaining to a broader audience.
Also agree with your point, SRE can go pretty broad in topics.
I am btw (because you asked in your video) a SRE Lead/Manager.
Thanks Lee for your feedback and for sharing your valuable knowledge as an SRE lead here in the comments with others as well. There is definitely a need for more information on these topics in the community.
Moving from Opps to SRE . Great introduction - directly to the point for tech people. Well done.
Good video. I think what you explained as SLA is actually SLO. SLA is more of a commercial agreement that specifies kind of fine when you fail to meet SLO. You also missed one very important topic which is SLI.
I'm a second year computer science student and this is the very first time I've ever heard of such a role named site reliability engineer. I guess there's still a lot to learn. Great video though❤❤
I am a SRE for many years , the video is just awesome
👏
I was looking for this video to explain on SRE. Thanks a lot to hear us and making this.
My pleasure! I'm really glad that the video is helpful for you guys!
Working as SRE, mostly doing the same stuff, Automation, Monitoring, On support call, etc... Loving it :)
As an SRE I like building and setting up the tools. For example writing scripts that detect changes and alert based on those incidents. But actually handling those incident is a pain in the ass because it involves a lot of communication with other people, emails etc
7:14 - What SRE tries to do
9:17 - SLA
11:00 - Nines
11:18 - SLA - not only about time (Errors rate for example)
One of the best thorough and comprehensive explanations of SRE, or I must say, THE BEST! I love the comparison part between SRE and DevOps so much! Thank you for your work and knowledge, Nana!!
Very Good and thorough presentation. Kudos, you are gifted.
Awesome explanation. Now I have better clarity regarding SRE and DevOps.
Thanks Sujeet, happy I could clear your doubts about it :)
Great description and comparison .Thanks a lot Nana, you are doing a great job
First time as an SRE thank you for sharing this video it helps me well :)
The presentation and content are very nice, greatly describing things by animation.
Ma'am, please make a video on what is the role of a Developer Advocate and What is Chaos Engineering ??
When you explain SLA you are really talking about SLO. The SLA is an agreement with some kind of consequences, usually financial. SLO is the objective that defines the availability, as an example, and the SLIs are the indicators you measure it with.
Nana your content is so good and relevant. Thank you!
Thank you Erik! 💙
What a timing Nana, great content as always, thanks for the much helpful info... Thankful for ur service
Just AMAZING , Keep it Up Nana 👏👏
My favourite Tech instructor
Great videos! Also watched the DevOps one, I especially appreciate how you address the ambiguities. My 2 cents on DevOps and SRE: are they almost the new Dev & Ops, but an upgraded version where both sides now need to have a broader knowledge of the full software life cycle. At the end of the day, each side still have their priorities (speed or reliability) as you can't really ask people to care about everything.
I thought SRE was a made up role when I was offered the position at my company. Whew, little did I know. I'm 2 months into it and this little software dev / software QA automator is swimming in a firehose of education. So much new to learn.
interesting to see the difference between practical devops and sre. we have a team of devops engineers, but you can see who acts more according to the sre or practical devops roles.
You are my favorite teacher 👩🏼🏫, I’m Chinese, I like your voice,😀
Thank You Nana, Awesome explanation !!
Happy to hear! 🤗
Thanks for the awesome video.Love the visualization and presentation❤️
I too do love them... I don't know how she does them and where to get the templates...
Thanks Jayanth, happy you like the visuals :D
What app do you use to make them? And where do you get the templates?
I'm working as SRE recently, I'm thinking both are the same. Thanks for the video.
Hiiii
I’m a fresh graduate in computer science can I get an entry level job as SRE
Very well defined. Thanks.
I recently transitioned from an information systems engineer to an SRE. Our current company’s goal for this role is to create a CI/CD pipeline, since it does not exist yet. However, we want to be able to monitor and keep our systems up and reliable moving forward.
Fascinating. My take on this is it sounds like a modern, cloud native version of what Sys admins would do back in the day.
Awesomeness and Information Overloaded! Thanks!
I’ve been waiting patiently for this 🤩
About SRE, this is best video to explain.
Thank you. Great video.
So, to summarize, in the past we had two teams with different objectives: Devs for speed, Ops for reliability.
And now we have 2 teams with "different" objectives: SRE for reliability and observability and DevOps for speed in releases and infra provisioning.
Nice 🙂👍
I don't agree with that statement.
SRE cares about reliability and observability, they can be either included in teams or act as a consultant to the different teams.
They mainly drive improvements forward and will help the teams achieve that next level on topics like reliability/scalability/performance/observability.
In regards to your DevOps team, in a "you build it you run it" way, the teams will take the tasks of deployment and infra provisioning on themselves because they have all the know-how of the application. Unfortunately in many bigger/older companies, this is not true and you have siloed teams (dev/infra/qa...).
Note: I don't like the term DevOps team, it's a philosophy and not a role.
To add to what @Lee Van Steerthem said SRE's usually also provision infrastructure. In my org I am an SRE but our team is called AWS platform team.
@@azzy6543 For me that's indeed a platform team, not SRE. However many teams in the organisation can help and mature reliability within their team without being called SRE.
However I would not consider the platform team to be true SRE's as they might have not enough influence on the application code itself.
ქართულადაც რომ გააკეთო ვიდეოები dockerზე ძაან მაგარი იქნება🖤🖤🖤
I've never before came across a 30 seconds ad in the TH-cam video that I can't skip. This is the next level.
The content is interesting though.
Really? I have disabled non-skippable ads explicitly
Great video!! :) I was wondering what the difference is between the two. My question now is what tools and skills should SREs focus on or have? :)
ქართულადაც რომ დაიწყო ახსნა ძალიან კარგი იქნება ❤️
Very nice explanation Nana.. I clearly understood SRE and how it really works.. Thanks for the clear explanation video.
Thank you Nana, always giving us amazing content
Another good job Nana! Thank you!
i learn a lot with your videos!! cheers from argentina!!
Great to hear Marcos!
Overall, a good video. However, your explanation of SRE's role is around logging, monitoring and alerting. I thought I heard you say SRE's role is also to ensure what impacts new changes will have on the reliable and that this is through automation. And that this enables developers to push code more frequently. Other than the mention, I didnt hear how SRE does that. Specifically what are they automating to ensure new changes wont affect the site reliability. Is there more to an SRE other than logging, monitoring, alerting and post mortem?
Release Engineering role - contol what goes in n which feature is enabled/disabled in which all environments in a well controlled manner.
Thank You mam....Please make a series of videos on SRE
The last segment is the best. I've been an SRE for 6 years or so now and never really noticed that we flip-flopped "personalities". In the 200X's ops wanted to slow the releases, congrol changes, etc. to keep things stable, while developers wanted to crank out chnages quickly with no care to stability. Fast forward to today and we've flipped. Now, the SRE (developers) want to focus on reliability while DevOps (Ops) want to crank up the speed of releases.
Great Content!
I would appreciate your effort nana 👍
Well explained, thanks.
@Techworld with Nana kindly mount a bootcamp on SRE, i am interested.
Thank you Nana for detailed explanation 👏👏👏. I had confusion between SRE and Devops. I am 1 hr late to watch this 🤣😭😂
Thanku for amazing content
Thanks @nana for sharing this video, Great game, as usual :-)
I would like to challenge a little bit the sillos we are trying to create between DevOps ( Build ) and SRE ( Run ) .
A DevOps Engineer should not focus only on speed, but also on quality , as you mention in your video. SRE is a critical task to ensure we deliver with quality, and is part of the so valuable feedback loop of DevOps.
In case the team size grows, once could isolate the roles within a team, but I would rather recommend to keep these people in the same team and exchange the roles in a monthly basis, so they can share the same goal and manage their skills accordingly.
Side question: SLA is a key metric to monitor, but I usually found people building their own in house grafana dashboard to observe and alert. Any counter proposal to harmonize this asset?
Can you please advise on the technologies to learn for a SRE role?
As usual very clear with Realtime tools whiteboarding
Nana I love you. The best teacher in town
Amazing videos ! I like so much your channel. Congrats nana and thank you !
Thank you Nana..helping me now..great 👍
Nana u are just awesome... this video helped a lot
Amazing video, Thank you 😊
Nana rocks!
Very well explained.... I had a few gaps in understanding how SRE is different from DevOps ... your video covered all those gaps ... thanks a lot Nana for the wonderful explanation !!!!!
Thank you! Appreciate your positive feedback! 💙
as usual, another masterpiece from NANA!
Thanks Nana. Really very well explained! If possible can you please try to add more videos SRE. May be some scenarios that you have seen in SRE
Which software do you use for designing such an awesome presentation? Thank you Nana for making this video.
Very insightful thank you! Now I know the difference :)
This was a really good video. Thanks a ton!
Thanks for the video.
I'm working as SRE currently, I think, besides the monitoring and alerting tasks, we also have response to incidents - PRODUCTION tasks which "DEVOPS" doesn't do.
Hi sir, Does SRE having Good Carrier Growth? In case, i looking to stage in IT for future
your videos are top notch :)
Congratulations on one more incredible video. Love your visual content
I wish you'd take about how configuration management helps with site reliability
Thank you for the great content! Looking forward to subscribe and learn further with your channel 😊
Thank you so much as always amazing video
Thanks 💙💜