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

Service-Oriented Architecture: There and back a...

Service-Oriented Architecture: There and back again...

At TaskRabbit, we split up our “monolith” into several services with varying degrees of success. It worked from a team organizational perspective but there were unexpected downside in ops, testing, and agility. We tried again along a different axis with more success and solved the noted issues by putting the apps in a single repo.

Conclusions…
Separation and namespacing is the key. It’s about service area of changes, not git repos
One project eases the pain of testing and deployment
Your architecture does not have to match your organization
SOA and/or microservices are talked about a lot, but each case is different.

Brian Leonard

November 10, 2015
Tweet

More Decks by Brian Leonard

Other Decks in Technology

Transcript

  1. mono·lith noun \mä-nə-lith\ a single-2ered so5ware applica2on in which the

    user interface and data access code are combined into a single program from a single pla<orm.
  2. mono·lith noun \mä-nə-lith\ a single-2ered so5ware applica2on in which the

    user interface and data access code are combined into a single program from a single pla<orm. a label so5ware developers give an applica2on they are working on, o5en while complaining that things aren’t going as quickly as they once did.
  3. There and back again •  Microservices can be good • 

    Separa2on is the key •  One project eases pain •  Architecture != Organiza2on