Scalability blog post: What we learned about iteration as a new team in infrastructure - 2020-11-09

Proposal

The Scalability team have recently been working on improving GitLab's use of Redis, one of our primary datastores. We've been working on increased monitoring and observability (gitlab-com/gl-infra&212 (closed)), improving problem areas that we found as a result of that (gitlab-com/gl-infra&259 (closed)), and sharing the knowledge we found with the wider community.

Checklist

• If you have a specific publish date in mind (please allow 3 weeks' lead time)
  • Include it in the issue title
  • Give the issue a due date of a minimum of 2 working days prior
  • If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
• If time sensitive
  • Add ~"Blog: Priority" label and supplied rationale in description
  • Mention @rebecca to give her a heads up ASAP
• If wide-spread customer impacting or sensitive
  • Add sensitive label
  • Mention @nwoods to give her a heads up ASAP
• If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS, apply the Partner Marketing label, and see the blog handbook for more on third-party posts
• If the post is about one of GitLab's customers, mention @KimLock and @FionaOKeeffe, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts
• Indicate if supporting an event or campaign
• Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)