Emergent Distributed Architectures

Emergent Distributed Architectures

Peter Bourgon and Sean Braithwaite offer an overview of microservices and data pipelines, explaining how both systems reflect the organizations and people that build them (in adherence to Conway’s law) and can be well understood in terms of their relationship to change and time. You'll learn the virtues and vices of each architecture and get enough context to apply them coherently.

45a07e96e3060fb22f7db34d9edf2c14?s=128

Sean Braithwaite

October 18, 2018
Tweet

Transcript

  1. 1.

    Microservices and Data Pipelines — Sean Braithwaite @brapse · Peter

    Bourgon @peterbourgon · Velocity London 2017 Emergent Distributed Architectures:
  2. 2.

    Microservices and Data Pipelines — Sean Braithwaite @brapse · Peter

    Bourgon @peterbourgon · Velocity London 2017 Emergent Distributed Architectures:
  3. 34.

    @brapse, @peterbourgon Emergent Distributed Architectures Microservices:
 Why? —To solve velocity

    gridlock. When? —It’s obviously necessary, and there are resources for automation.
  4. 36.

    @brapse, @peterbourgon Emergent Distributed Architectures Data pipelines:
 Why? —To enable

    collaboration between 
 domain experts. When? —Domain expertise varies, and
 coördination is expensive.
  5. 39.

    Microservices and Data Pipelines — Sean Braithwaite @brapse · Peter

    Bourgon @peterbourgon · Velocity London 2017 Emergent Distributed Architectures: