About SRGTechnical ArticlesRecruitment Information
About SRGTechnical ArticlesRecruitment Information
HOME/Technical Articles/It may be a little late, but I co-authored a book called "SRE Knowledge Map"

It may be a little late, but I co-authored a book called "SRE Knowledge Map"

This article isCyberAgent Group SRE Advent Calendar 2025This is the article for the first day. Since it's the first day, I've written it in a relaxed style.

Introduction

Tsuge (@shotaTsuge)is.
#SRG(Service Reliability Group) is a group that mainly provides cross-sectional support for the infrastructure of our media services, improving existing services, launching new ones, and contributing to OSS.

Looking back on 2025

This year, in my main job, I was not only the head of the cross-sectional SRE organization (SRG), but also the technology management of the entire CyberAgent Group (CTO General Office) and the EM area of the entire media & IP area to which I belong. In order to update this, I established the EM office and improved the EM area as the office manager. This year was a year in which my duties expanded compared to last year. As for SRG, I set the goal of improving strategic branding.Over the course of a year, he has written approximately 60 blogs and given approximately 20 presentations both inside and outside the company.We carried out the following.
Also,Promoting the evolution of innovative development organizations where engineers and AI agents work togetherIn order to achieve this, a specialized organization calledAI-Driven Promotion Office", I am also promoting the use of AI throughout the CyberAgent Group. I hope to share more about what the EM Office and the AI-Driven Promotion Office are working on in blogs and presentations at other events.
Outside of our main business, as in the previous year,SRE NEXT 2025I participated as a core staff member at the event. Last year, I was a co-chair and didn't have time to speak, but this year, although it was a sponsored session, I was able to speak at the event.CyberAgent Group's 10-year history of SRE and survival strategies in the AI era"I gave a presentation titled "
In addition, based on his experience of promoting SRE to services and organizations for over 10 years,SRE Knowledge MapI am one of the co-authors of the book "How to Become a Better Person." It has received a lot of positive feedback on social media, which makes me very happy as one of the authors.
In this article, I would like to briefly talk about what I was thinking and what I was unable to write when writing Chapter 8, "SRE Organizational Structure," which I was responsible for in "SRE Knowledge Map."

SRE Knowledge Map: Chapter 8, "SRE Organizational Structure"

Chapter 8 of the SRE Knowledge Map: "SRE Organizational Structure"This chapter describes the organizational structure of SRE, which is important for promoting SRE practice. Chapter 8 is structured as follows:
  • 8.1 The Importance of Organizational Structure in SRE
    • 8.1.1 Challenges the SRE team faced in an environment lacking organizational support
    • 8.1.2 Conway's Law and the Reverse Conway Strategy
    • 8.1.3 Summary of the importance of organizational structure in SRE
  • 8.2 Tips for considering SRE organizational structure
    • 8.2.1 Team Topology
    • 8.2.2 SRE's place in the team topology
    • 8.2.3 SRE and Team Topology
    • 8.2.4 Summary of tips for considering SRE organizational structure
  • 8.3 SRE Organizational Patterns
    • 8.3.1 Three organizational patterns
    • 8.3.2 SRE Organization Allocation
    • 8.3.3 Summary of SRE organizational patterns
  • 8.4 SRE Implementation Models and Patterns
    • 8.4.1 Three SRE Implementation Models
    • 8.4.2 Embedded Type
    • 8.4.3 Centralized
    • 8.4.4 Hybrid type
    • 8.4.5 Summary of SRE implementation models and patterns
  • 8.5 How to Choose an SRE Implementation Model and Pattern
    • 8.5.1 Organize patterns that require SRE
    • 8.5.2 Selecting the right SRE implementation model and pattern for your organization
    • 8.5.3 Summary of SRE implementation models and patterns
  • 8.6 Summary

What I was thinking about when writing

When I was first asked to write about organizations in this book, I decided to publish it as soon as possible through O'Reilly, as this is the first book on SRE to be written in Japanese.SRE Book（SRE Site Reliability Engineering or Getting started with SRERather than simply summarizing the content of other books, I wrote this chapter with the intention of redesigning it in a way that incorporates the insights and practices I have gained from my many years of experience in SRE organizational design. Because of this background, I had to rewrite it many times, making it a very difficult chapter to write. I am truly grateful to everyone who reviewed it.
It is explained in the bookThree organizational patternsandThree SRE implementation modelsThis is a summary based on my own experience.

Three organizational patterns

  • Product-specific pattern: SRE team dedicated to a single product
  • Cross-product patterns: SRE team responsible for multiple products
  • Cross-company pattern: SRE teams are responsible for multiple companies and products

Three SRE implementation models

  • Embedded typeA model in which specialized roles within an organization (in this case, site reliability engineers) directly participate in and work as a unified team with other teams.
    • Product SRE and Embedded SRE
  • centralizedA model in which SRE teams and functions are centrally managed within an organization and work to improve reliability with a unified perspective and approach.
    • SRE Center of Practice and Platform SRE
  • Hybrid typeA model that combines the characteristics of both embedded and centralized systems.
For more details on the three organizational patterns and the three SRE implementation models, please purchase the book. We also hope that the book will help readers select the SRE implementation model and pattern that best suits their organizational challenges and needs.SRE implementation pattern selection treeWe have also made it publicly available, so we hope you will make use of it.8.5.3 Summary of SRE implementation models and patternsAs mentioned in the previous section, even if you design your organization exactly as written, it may not always work out well, so don't be afraid of change.Customize implementation models and patterns to suit your organizationAlso, considerA dedicated SRE isn't necessarily requiredDon't forget that.

What I couldn't write

Due to the deadline for writing, I would like to cover some of the topics that I was unable to include in this book. AI technology is evolving at a speed that exceeds many people's expectations. Just as it is for promoting SRE practice, organizational structure is also very important in promoting the use of AI. Although I was unable to write about it in this book, some people may be interested in how SRE organizations will change in the AI era. In fact, SRG is also promoting the use of AI, and the use of AI technology is expanding widely beyond the SRE field, including output enhancement and management. SRG also provides support for businesses and services in the areas of infrastructure and SRE, as well as AI utilization.
In addition to simply utilizing and supporting AI, SRG aims to create an AI SRE team, with the goal of having a functioning AI SRE team by the end of 2026. To achieve this, we need to implement a centralized implementation pattern,SRE Center of PracticeI think this will become extremely important.

Conclusion

Recently, I've been hearing a lot about whether SREs will continue to be necessary in the age of AI. I think this is due to the improved quality of generative AI as a result of advances in AI technology, but personally, I believe there will continue to be a need for SREs. However, depending on the size of the organization, I believe the scope of responsibilities and approach of cross-functional SREs, as well as the technical areas they should focus on, may change. I hope to discuss this topic on another occasion. If you're interested, please invite me for drinks or to an event.
Once again, I hope that this Advent Calendar will help many people learn about our group's efforts. Personally, I'm looking forward to it.
Tomorrow,@ishikawa_kumo is.
If you are interested in SRG, please contact us here.