Session Name: Architectural Patterns for DevOps and SRE Teams
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 change, 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. 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 contraindicated conditions where patterns may not be recommended"
Marc works for IBM in Southern California and is currently an SRE Architect and Senior Technical Staff Member in IBM Automation portfolio. Marc also teaches courses part-time at California State University, Fullerton. Marc has over 20 year’s experience in the Software Engineering industry with a focus on: server development, cloud development, system integration, devops, containerization and cloud orchestration, SRE, system verification and testing. Marc has a Bachelor's and Master’s of Science in Computer Science and a Master's of Science in Software Engineering from California State University, Fullerton. Marc is an IEEE Senior Member, the Chair for OC ACM, Chair of the Southern California IBM Hispanic Resource Group.