As organizations begin to work on numerous services and components many are faced with a new set of challenges.  Adding to these challenges is the ever increasing remote and distributed workforce.  This places a significant operational and tooling overhead on standard development teams. Each team needs its own pipeline, monitoring-alerting, on-call staff, etc.  It is not enough for teams to be agile in coding and systems, teams need to understand how a change can affect a distributed system.  With new service frameworks focusing on community pipelines, enhanced collaboration, and team ownership, sanity can exist.  Pipeline as a Service can help force organizations transformation into Community DevOps.

In this session we will discuss how Community DevOps can enable teams to mange the complexity of modern development from ideation to production.  We will discuss how pipeline as a service provides the right balance of ownership from a single team to an enterprise, the technical components and how to avoid common pitfalls.

 

 

 

 

 
1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Problem Context
  • Distributed Systems & Workforce
    • Team structure
    • Operational/Tooling Overhead
  • Community DevOps
  • Pipeline as a Service
    • Architecture/components
  • Benefits of an Enterprise Service Framework 

Learning Outcome

Obtain an understanding of some common challenges of distributed systems and workforce
- Understand the concept of service frameworks: Community DevOps
- Learn what Pipeline as a Service is - practices and tooling
- Understand how to break up pipelines for a specific service and for the distributed system.

 

Target Audience

Coaches, Engineers, ITPMs

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal