According to Google, SRE is what you get when you treat operations as if it’s a software problem. In this video, I briefly explain how SREs engage with other teams especially service owners / developers.
Youtube channel here: https://youtu.be/EgpCw15fIK8
4. PRR - Product Readiness Review
• PRR can be started at any point of the
service lifecycle
• SRE seeks production responsibility for
important services for which it can make
concrete contributions to reliability
• SRE is concerned with several aspects
of a service, which are collectively
referred to as production
4
5. PRR - Product Readiness Review
5
System
architecture and
interservice
dependencies
Instrumentation,
metrics, and
monitoring
Emergency
response
Capacity planning
Change
management
Performance:
availability, latency,
and efficiency
6. PRR
• The objectives of the PRR are as follows:
• Verify that a service meets accepted standards of
production setup and operational readiness, and that
service owners are prepared to work with SRE and
take advantage of SRE expertise.
• Improve the reliability of the service in production, and
minimize the number and severity of incidents that
might be expected. A PRR targets all aspects of
production that SRE cares about
6
8. Evolving the Simple PRR Model:
Early Engagement Model
• The service implements significant new functionality and
will be part of an existing system already managed by
SRE
• The service is a significant rewrite or alternative to an
existing system, targeting the same use cases
• The development team sought SRE advice or
approached SRE for takeover upon launch
8