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

Microservices Meet Real-World Projects: Lessons...

Microservices Meet Real-World Projects: Lessons Learned @ Microservices-Meetup-Rhein-Main

Alexander Heusingfeld

February 21, 2017
Tweet

More Decks by Alexander Heusingfeld

Other Decks in Technology

Transcript

  1. Domain Architecture -Which boxes? -Use Cases -Semantics & Purpose Macro

    Architecture -What’s in between? -Protocols, Deployment …so we show the different levels of decisions…
  2. Domain Architecture -Which boxes? -Use Cases -Semantics & Purpose Macro

    Architecture -What’s in between? -Protocols, Deployment Micro Architecture -What’s inside? -Component internals …so we show the different levels of decisions…
  3. “Don’t care about this, it’s our business!” “Alarming is our

    concern, don’t bother about it!” “No need for a discussion, we always fix that during deployment.” “That’s part of the handover to operations.”
  4. overcome “us vs. them” > cross-functional != cross-department > have

    one manager to decide on a team’s targets > don’t neglect team-building
  5. overcome “us vs. them” > cross-functional != cross-department > have

    one manager to decide on a team’s targets > don’t neglect team-building > trust is not optional
  6. The manageable, domain specific scope enables the development, operation and

    maintenance of an SCS by an autonomous team. Team 1 Team 2 Team 3
  7. Conway’s Law “Organizations which design systems are constrained to produce

    systems which are copies of the communication structures of these organizations.” – M.E. Conway Organization ˠ Architecture
  8. What this taught us > enable fast feedback for your

    team > automate what’s next to you first
  9. What this taught us > enable fast feedback for your

    team > automate what’s next to you first > do your homework before you teach others
  10. What this taught us > enable fast feedback for your

    team > automate what’s next to you first > do your homework before you teach others > other people will notice the benefits
  11. What this taught us > enable fast feedback for your

    team > automate what’s next to you first > do your homework before you teach others > other people will notice the benefits > complex processes can be adopted, divide them and take one step at a time
  12. https://www.flickr.com/photos/cornelii/531691572 https://www.flickr.com/photos/cornelii/531691572 • pets • have names & take time

    • individual care • you usually only have 1 to 3 of them • when they get sick -> take them to the doctor
  13. https://www.flickr.com/photos/cornelii/531691572 https://www.flickr.com/photos/cornelii/531691572 • pets • have names & take time

    • individual care • you usually only have 1 to 3 of them • when they get sick -> take them to the doctor
  14. https://www.flickr.com/photos/cornelii/531691572 https://www.flickr.com/photos/cornelii/531691572 • pets • have names & take time

    • individual care • you usually only have 1 to 3 of them • when they get sick -> take them to the doctor • cattle • you probably know how many you have • maybe their number • they mostly care for themselves • new ones are born, old ones die • if they get seriously sick -> kill them
  15. Service 2 Frontend Switch Monolith Module 1 Service 3 Service

    4 Customer Request Service 5 Reverse Proxy
  16. Summary > distributed systems are hard - organizational impact, too

    > don't forget: there's always at least one other perspective
  17. Summary > distributed systems are hard - organizational impact, too

    > don't forget: there's always at least one other perspective > Don’t overwhelm people, change one thing at a time
  18. Summary > distributed systems are hard - organizational impact, too

    > don't forget: there's always at least one other perspective > Don’t overwhelm people, change one thing at a time > not everyone who wants microservices is immediately capable to establish them
  19. Tammo van Lessen | @taval [email protected] Alexander Heusingfeld | @goldstift

    [email protected] Thank you! Questions? Comments? innoQ Deutschland GmbH Krischerstr. 100 D-40789 Monheim am Rhein Germany Phone: +49 2173 3366-0 innoQ Schweiz GmbH Gewerbestr. 11 CH-6330 Cham Switzerland Phone: +41 41 743 0116 www.innoq.com Ohlauer Straße 43 D-10999 Berlin Germany Phone: +49 2173 3366-0 Ludwigstr. 180 E D-63067 Offenbach Germany Phone: +49 2173 3366-0 Kreuzstr. 16 D-80331 München Germany Telefon +49 2173 3366-0 https://www.innoq.com/en/talks/