Architecture is often defined as the layout and usage of components based on external and internal constraints. Devops and SRE Teams are built around any number of services, but as services and the organizational landscape changes, team architecture can and should change to find the right fit based on the external and internal forces. This session is a conceptual session discussing architecture team patterns, yet technical topics will be covered encompassing Devops and SRE responsibilities and tooling.

I Architecture and Devops/SRE Teams – 10 min
A. Architecture as a reflection of constraints
B. Devops and SRE teams as a reflection of constraints
II. Devops and SRE Team Architectural Patterns - 20 min
A. Single team single service
B. Disparate teams/services
C. Consolidation of services
D. Hybrid consolidation and disparation
E. Disparate teams and guild skill
F. Legacy systems and next gen consolidated teams
G. Consolidated legacy systems and separate next-gen teams – the goldfish bowl isolation of technical debt
III Summary and Q&A 15 min

Key takeaways are as follows:
**The types of Devops and SRE Team Architecture Patterns, patterns that describe team composition, responsibilities, interactions
**The constraints that may make some patterns more tolerable or desirable than others
**The downsides of some patterns or anti-patterns or contra indicated conditions where patterns may not be recommended