In part one of this series, we discussed some of the key principles to consider when developing geographically distributed (GD) SRE teams. Similar to the first article, we’re leveraging the journey of LinkedIn’s SRE team as the point of reference for the topics discussed here in part two. Within this post, we’ll discuss growth planning, the challenges associated...
devops Articles
-
-
Why geographically-distributed SRE teams? In today’s hyper-connected technological world, there is a need for geographically widespread technical teams to facilitate global growth. Businesses that scale to this level need global teams to handle that reach. However, as development teams continue to ramp, it quickly becomes infeasible for them to solve operational...
-
Co-authors: Bef Ayenew and Adam Hobson Consider the following conversation that used to be typical at LinkedIn: "Folks, we may have an on-call problem this week..." "What’s wrong?" "Our Android engineer is missing." "Where are they?" "They’ve been on leave for two weeks now." "?!?!&*?!?!" Welcome to the on-call rotation for the LinkedIn flagship mobile app and...
-
I commute 3000 miles every day. Virtually, of course. LinkedIn's operations team uses technology to help bridge the thousands of miles...
- Topics:
- Developer Productivity,
- devops,
- day in the life,
- SRE
-
At LinkedIn, we love to build new things and explore new technologies. For the past year we've sunk our teeth deep into SaltStack, a...
- Topics:
- devops,
- infrastructure,
- Meetup,
- SRE
-
Editor's note: This blog has been updated since publishing. When I started at LinkedIn a little over a year ago the company had just...
- Topics:
- monitoring,
- operations,
- devops,
- metrics,
- Kafka,
- SRE