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

Microservices - To hell and back

Microservices - To hell and back

Do's and don'ts when you move from a legacy monolith to micro-services.

The experience of being wrapping up a bunch of micro-services under a single API.

What, and how to test when you are 100% using micros-services.

And how to keep the micro-services mindset consistent.

Rubens Stulzer

May 10, 2017
Tweet

More Decks by Rubens Stulzer

Other Decks in Programming

Transcript

  1. Listings V1 to V2 • Same Contract • Zero maintenance

    on Clients • Lot’s of work on mappings
  2. Client calls /v1/listings/report => Publishers API Publishers API calls =>

    Listings API Listings API calls => LQS -> which reads from a DB => Leads API => Calls Account API Accounts API | -> reads from DB => Call SalesForce
  3. Kill "Microservices" before its too late - Chad Fowler https://www.youtube.com/watch?v=-UKEPd2ipEk

    The Majestic Monolith - DHH https://m.signalvnoise.com/the-majestic-monolith-29166d022228 Monolith First - Martin Fowler https://martinfowler.com/bliki/MonolithFirst.html