Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Service Oriented Harmony

Service Oriented Harmony

MonoRail apps (or monolithic Rails applications) are so 2010. Service Oriented Architecture offers some great solutions to simplifying app complexity, but breaking applications into services trades code complexity for communication complexity. Building interconnected features that require two services to be changed simultaneously can test your confidence in SOA as a solution to complexity. This talk covers some great patterns and anti-patterns for managing development work across teams and services in your shiny new service oriented architecture.

Jesse Toth

May 12, 2013
Tweet

More Decks by Jesse Toth

Other Decks in Programming

Transcript

  1. Service Oriented Architecture a system made up of several composable

    parts, called services, that work together to make up a single application Monday, May 13, 13
  2. Scaling ✤ bottlenecks ✤ deployment ✤ too big to fit

    in your head at once Monday, May 13, 13
  3. Scaling ✤ bottlenecks ✤ deployment ✤ too big to fit

    in your head at once ✤ ramping new people up = :( Monday, May 13, 13
  4. Scaling ✤ bottlenecks ✤ deployment ✤ too big to fit

    in your head at once ✤ ramping new people up = :( ✤ too many cooks in the kitchen Monday, May 13, 13
  5. difficult to extract into services everything interconnected services written, thrown

    away, and rewritten any change requires touching multiple codebases Monday, May 13, 13
  6. Conway’s Law organizations which design systems are constrained to produce

    designs which are copies of the communication structures of these organizations Monday, May 13, 13
  7. Conway’s Law :: Restated we must model our team and

    communication structure after our desired system structure if we want it to succeed Monday, May 13, 13