worked mostly on Ops team ➔ Became SRE | DevOps almost 5 year ago ➔ I love to travel ➔ I believe DevOps is more culture than role ➔ In favor of gender equity and pro diversity ➔ Work at Hostelworld as SRE linkedin.com/in/julialamenza/ [email protected] JULIA LAMENZA
born at Google in 2003, when the first team of software engineers was tasked to make Google’s already large-scale sites more reliable, efficient, and scalable. @jlamenza18
development and operations. They split their time between operations/on-call duties and developing systems and software that help increase site reliability and performance. @jlamenza18
aspect. You don’t do Devops buying cool tools. ➢ SRE is the practice of creating and maintaining a high availability service, you can say that SRE is the sysadmin's fashion friend. @jlamenza18
part and SRE more on the aspects like system availability, observability, and scale considerations ensuring your service. @jlamenza18 DevOps and SRE can still be confusing at some level but it all depends on the company and your job profile interpretation.
We are more Ops than Dev ➢ 90% is inside DataCenters ➢ Migrate applications to cloud will be our main challenge ➢ We will have some changes inside our team by 2020 @jlamenza18
the service provider uses for the goal. Service Level Objective is a goal that service provider wants to reach. Service Level Agreement is a contract that the service provider promises customers on service availability, performance, etc. The SLA, SLO, and SLI are based on the assumption that the service will not be available 100%. Instead, you need to determine a value for this availability, for example, 99.5%.
can’t expect the success in implementing SRE| DevOps in one or two days. It may take days, weeks, and months to get matured. ➢ Software no longer stays within role boundaries, shouldn't be different within companies